Questions PBB

Questions with regard to PBB:

1. Is it legal to give my Personal Book to other and also to put it on my website?

2. Is it possible to rename a PBB file? For example

a4243987c60d43f7a8fad94956dd1150.lbspbb to AHBogaards_Theology.lbspbb? I tried it, but the result was that I could not find it in my Library.

Find more posts tagged with

Comments

MJ. Smith

1. Is it legal to give my Personal Book to other and also to put it on my website?

Only if you own the copyright.

2. Is it possible to rename a PBB file?

I don't think so.

TCBlack

Logos is, as I understand it, working on a sharing mechanism for PBB beyond simply putting it on personal websites (though that may also be available). Right now the only way to share L4 PBB's is to provide another L4 user the source document to compile.

AH Bogaards

https://community.logos.com/discussion/comment/271899#Comment_271899

Can someone of the staff of Logos give me an answer?

Tonya J Ross

1. Is it legal to give my Personal Book to other and also to put it on my website?

As MJ indicated, if you are the original author of your document you may feel free to distribute your content any way you wish. If there is copyrighted information contained in your document it is your responsibility to obtain the rights to such content you may need for public distribution. A good overview of such issues can be found here: http://en.wikipedia.org/wiki/Fair_use

2. Is it possible to rename a PBB file? For example

a4243987c60d43f7a8fad94956dd1150.lbspbb to AHBogaards_Theology.lbspbb?

I think you answered your own questions by trying it. [:)] No, you cannot rename the .lbspbb files themselves. You can rename your compiled book, however, by changing the title in the metadata in the Personal Book tool itself and then recompiling the book.

Mikko Paavola

https://community.logos.com/discussion/comment/271967#Comment_271967

Hi!

Thanks for the great update! I've been waiting PBB to have more Finnish (and English) resources to Logos.

As PBB is now available in 4.3 RC, it would be more than helpful to have better instructions for it. There's basics in http://wiki.logos.com/Personal_Books , but I'd need more detailed instructions. For example:

- How to tag Bible milestones that have several verses. For example I have a commentary that has Mt 13:24-30 and 36-43 in the same passage, and 31-35 after that. How should I code the milestone for Mt 13:24-30,36-43 (hyphen works but comma doesn't)?

- Can the compiler be teached to catch Bible verses that doesn't use the default English abbreviations of the Biblical books used by Logos? Is there some code I could add in the beginning of the document (for example Finnish abbreviations like 1.Moos.=Gen, 2.Moos.=Ex, etc.)? Or if there's no book mentioned but just the chapter and verse (for example just "(13:31-35)" in the commentary of Matthew should be recognized as Mt 13:31-35)?

- How to make different type of resources, for example Bible harmony or interlinear?

About the sharing: Can I send a PB to my colleague as a file so that he can open it in his Logos? What he shoud do to add it to his resources?

Thanks!

- Mikko

Lynden O. Williams

https://community.logos.com/discussion/comment/271999#Comment_271999

Can I send a PB to my colleague as a file so that he can open it in his Logos? What he shoud do to add it to his resources?

Not at this time. You need to send him the completed word document, and teach him how to compile it. When the release candidate goes gold, everyone will have the ability to build PBB, until then he will need to update Logos to the current release candidate.

Not able to answer the other questions, as I am still learning.

Dave Hooton

https://community.logos.com/discussion/comment/271999#Comment_271999

How to tag Bible milestones that have several verses. For example I have a commentary that has Mt 13:24-30 and 36-43 in the same passage, and 31-35 after that. How should I code the milestone for Mt 13:24-30,36-43 (hyphen works but comma doesn't)?

Try inserting them as below (rough syntax):

[[Matt 13:24-30]]

[[Matt 13:36-43]]

Text or Overview

[[Matt 13:31-35]]

Commentary on these.

[[Matt 13:24-30]] [[Matt 13:36-43]]

Text or Overview

[[Matt 13:31-35]]

Commentary on these.

There might be an issue with 31-35 appearing out of sequence.

Mikko Paavola

https://community.logos.com/discussion/comment/272120#Comment_272120

Dave: Thanks. It works, stays in sync with Bible. The only minus is that locator bar doesn't show Mt 13:36-43 at all, just Mt 13:24-30.

Is there somewhere complete list of codes that can be used in PBB? I'd like to code resources, but can do just the basics.

Dave Hooton

https://community.logos.com/discussion/comment/272180#Comment_272180

Dave: Thanks. It works, stays in sync with Bible. The only minus is that locator bar doesn't show Mt 13:36-43 at all, just Mt 13:24-30.

You might create a bug report in the PC Beta forum and upload your docx file (or just the relevant part).

Is there somewhere complete list of codes that can be used in PBB? I'd like to code resources, but can do just the basics.

We're being spoon-fed by Logos at present so the wiki article on PB's is pretty much it. You might also check some of the recent posts in PC Beta. However, the wiki does state that you can label a datatype link --> [[label|datatype:reference]] e.g.

Use [[3:16|Bible:Jn 3:16]] to provide a contextual reference to John 3:16

Dave Hooton

https://community.logos.com/discussion/comment/271999#Comment_271999

- Can the compiler be teached to catch Bible verses that doesn't use the default English abbreviations of the Biblical books used by Logos? Is there some code I could add in the beginning of the document (for example Finnish abbreviations like 1.Moos.=Gen, 2.Moos.=Ex, etc.)?

You would have to use something other than the Bible datatype; see http://community.logos.com/forums/p/35157/266882.aspx#266882

Mikko Paavola

https://community.logos.com/discussion/comment/272256#Comment_272256

- Can the compiler be teached to catch Bible verses that doesn't use the default English abbreviations of the Biblical books used by Logos? Is there some code I could add in the beginning of the document (for example Finnish abbreviations like 1.Moos.=Gen, 2.Moos.=Ex, etc.)?

You would have to use something other than the Bible datatype; see http://community.logos.com/forums/p/35157/266882.aspx#266882

Hi! I couldn't find anything related to this problem from that thread. The problem is: PBB will recognize Bible verses from the text and will create a link automatically (for example "Gen 1:1"). But if the text has other than English default abbreviations (like "1.Moos.1.1" in a Finnish commentary), it's not recognized automatically and I need to code it manually, that means too much work if there's hundreds of verses to code. It would be much easier if I could define that "1.Moos." should be counted as Genesis.

Another questions, this time about making a PB Bible:

- Where should I exactly place the {{field-on:Bible}} ... {{field-off:Bible}} tags? Do I need to put them to the beginning and end of every verse, or is it enough to put them to the beginning and end of a chapter/paragraph (to leave just chapter numbers / headings off)? And can there be code [[...]] inside the field, or does all the codes need to be excluded from the field?

- Is there some code to show verse numbers automatically? If the code goes as follow: "[[@bible: Jn 1:1]]Bible verse text... [[@bible: Jn 1:2]] Bible verse text..." , how should I need to modify the code to get the verse numbers visible, or do I need to add the verse numbers to the Bible text itself?

Dave Hooton

https://community.logos.com/discussion/comment/272288#Comment_272288

Hi! I couldn't find anything related to this problem from that thread. The problem is: PBB will recognize Bible verses from the text and will create a link automatically (for example "Gen 1:1"). But if the text has other than English default abbreviations (like "1.Moos.1.1" in a Finnish commentary), it's not recognized automatically and I need to code it manually,

The point of that thread is that code for different bible versification schemes is not handled or documented. Finnish (or other language) schemes would include the book names.

- Where should I exactly place the {{field-on:Bible}} ... {{field-off:Bible}} tags?

You will have to experiment. It's basic intention is to separate bible text from verse numbers, pericopes, headings, etc. However, PBB should handle other code within bible text boundaries. eg. footnotes and verse milestones, but this is still very much untested.

EDIT: i think it will be tedious as you have to separate footnotes and verse milestones from bible text:-

...eternal life.{{field-off:bible}⁶ [[@Bible:John 3:16]] ¹⁶ {{field-on:bible}}"For god so loved the world,{{field-off:bible}

where ⁶ is a footnote, ¹⁶is the verse number. Note that punctuation is not searchable, so should be OK within the bounds of bible text.

Mikko Paavola

https://community.logos.com/discussion/comment/272388#Comment_272388

Thanks! I made some Bibles that way and it works. I found it easiest to put the Bible text to Excel document (one verse per line, columns: book, chapter, verse, text). I just made additional columns and put the codes in their places. After that I copy-pasted it to Word as a plain text and removed the tabulations from the whole document. Now I just need to add the book and chapter names as headings.

Another question about making a PB Bible: How the Bible place notes should be coded? (Sorry, I don't know how they are called in English, for example Matt 1:6 would have "1 Sam 16:1; 17.12" in a popup and info-panel.) Is there an own code for that or do we need to use just ordinary Word notes for them?

Also I haven't found a solution / answer for my earlier question:

How to make PBB to automatically recognize and tag the non-English Bible abbreviations (like 1.Moos., 2.Moos. Jes., Luuk., etc. in Finnish) in a commentary text. Coding them manually is too hard work.

Graham Criddle

https://community.logos.com/discussion/comment/273359#Comment_273359

Another question about making a PB Bible: How the Bible place notes should be coded? (Sorry, I don't know how they are called in English, for example Matt 1:6 would have "1 Sam 16:1; 17.12" in a popup and info-panel.) Is there an own code for that or do we need to use just ordinary Word notes for them?

Insert a Word footnote where you want the popup to occur and then code a PBB datatype link - of the form [[Bible:jn 3:16]] - in the footnote

Graham

Bohuslav Wojnar

https://community.logos.com/discussion/comment/273359#Comment_273359

How to make PBB to automatically recognize and tag the non-English Bible abbreviations (like 1.Moos., 2.Moos. Jes., Luuk., etc. in Finnish) in a commentary text. Coding them manually is too hard work.

Hello Mikko, I am not sure I have an answer for your question but it looks to me that it works differently withing languages offered by Logos in the PBB tool. I have made some Czech and Polish Bibles, using the respective language. In Czech I have to use Czech Bible Book abbrev. while in Polish I have to use English ones.

One more thing. The easiest way to put milestones and other tags into the Bible text (like {{filed-on:Bible}}) is to use functions Find and Replace, whether in Word or (what I prefer) I do it in HTML editor like PSPad (I save docx as HTML for that purpose), I also assign Headings etc. in the editor and only then I save it as docx. You can do a lot with Find and Replace in the MS Word itself also.

As for the {{filed-on:Bible}} {{filed-off:Bible}} tags, I found it works even across the chapters (not showing the name of the chapter in the Bible text field if the chapter is Heading2 or Heading3 etc.) but I use it at the beginning of each chapter and close the field at the end of the chapter. In case I have a Bible with notes and references, I tried to use it in every verse (to separate other text) and it worked. I also want to learn more about that (for instance if the field Bible and notes or Bible reference in between makes it part of Bible text or not.) I will experiment with that as time allows and let you know.

André Kamphuis

https://community.logos.com/discussion/comment/273366#Comment_273366

Could anybody tell me what I'm doing wrong with these data type links?:

[Cf. began
2:4 [2:4>> Bible: Acts 2:4]]; 11:4 [[>> Bible: Acts 11:4]], 15 [[>>Bible:
Acts 11:15]]

Shows up like this (second line):

Nothing happens when I hover over 11:4 or 15.

steve clark

https://community.logos.com/discussion/comment/279358#Comment_279358

PB will recognize full Bible verses (e.g. Book Chapter:Verse) without any tagging.

[2:4>> Bible: Acts 2:4]];

this one is missing the left [ (there needs to be 2 together with no spaces or characters between them)

[[>> Bible: Acts 11:4]],

You left out the Label item in these tags (e.g. [[Label >> Bible:Acts 11:4]]), also you need a space on both sides of >> for PB to recognize it.

This works

[[Acts 11:4 >> Bible:Acts 11:4]], [[15 >> Bible:Acts 11:15]]

produces:

As mention at the beginning full scripture references need no tagging see below:

And Acts 11:4, 15 (no tagging applied here)

produces:

André Kamphuis

https://community.logos.com/discussion/comment/279360#Comment_279360

Thanks a lot, Steve!

Andreas Holmberg

https://community.logos.com/discussion/comment/271999#Comment_271999

- Can the compiler be teached to catch Bible verses that doesn't use the default English abbreviations of the Biblical books used by Logos? Is there some code I could add in the beginning of the document (for example Finnish abbreviations like 1.Moos.=Gen, 2.Moos.=Ex, etc.)? Or if there's no book mentioned but just the chapter and verse (for example just "(13:31-35)" in the commentary of Matthew should be recognized as Mt 13:31-35)?

Hello Mikko

I compile books in Swedish. In the PB tool I choose Swedish as language. By doing so Logos automatically discovers all my abbreviated bible references such as 1 Mos or 1 Kung. I'm not sure it works for Finnish but try choosing Finnish in the PB tool before compiling you book. IF this works, NOTE that you must also use Finnish abbreviations in your bible-milestones in order for them to work and be detected by for example Passage Guides.