1534 Tyndale Bible PBB

When I try to build the PB it says I need a license. When I go to the suggested link on Logos.com, it says it can't find the file. I have ordered and pre-ordered everything Tyndale I can from Logos. What am I missing here?

For what its worth, it compiles just fine on my computer.

All you have to do is make a collection with these rules "edition:user" then your personal books with show up on every pc or mac that has Logos 5 installed.

well... its actually a little more complicated than that.

With the new beta, once it is released, they will all automatically sync. Until then, they only sync the meta data. If you try and open a book on a computer where the book has not been compiled it will give you a license issue error, and if that is clicked, it will take you to a page that doesn't exist on the logos store with another awkward error.

To get around that, you should compile all your PBBs on every computer you intend to use them on, or use a utility like drop box to sync files between computers, and then use the scan command to ensure they are all in the libraries of both pcs (or macs).

Much appreciated... thanks!

Many thanks for all your time and effort!

Really looking forward to reading something from one of the first English translators who suffered so much to make the Bible available to all.

I wonder if he had any idea how many English speaking people there would be who benefited what he started.[Y]

Thank you very much for your efforts, Mark. Much appreciated.

Welcome to the forums.  And you now know why searching the 'old' threads are a useful activity.

Hi Adrien:

Mark is now on staff with Faithlife, so I doubt he'll be able to reply. I can tell you what I know, if that helps.

First, here's a link to the Logos Wiki page for Personal Books, with general information you'll need for any type of personal book you make, bibles or otherwise:  https://wiki.logos.com/Personal_Books 

Here are some notes specifically regarding bibles:

1. You will want your personal book bible to behave as much as possible like a Logos-produced bible does. This will include, but isn't limited to, these functions:
1. 'Bible' index. Your bible will need an index to enable it to be in a Link Set with other bible-index resources, to be in a Multi-view with thos, to be able to be navigated by typing in the Reference Box, and to be discovered in a Milestone search.
2. The actual bible text will need to be tagged, so that Bible searches will find it, Text Comparison will work, Copy Bible verses will work, etc.
3. You will want book names to have MS Word 'Heading 1' style applied, chapter names to be in 'Heading 2'. This will make your Table of Contents pane useful. If your bible has pericope (or section) headings, those will need 'Heading 3' applied.
2. Here are examples of the tagging elements:
1. Bible Milestone. This is in the form of   [[@Bible:John 3:3]]  When your PB is compiled, these tags will provide the Bible index.
2. (Optional):  If you want to be able to mouse-over a verse number and see your Preferred Bible for that verse, use this tag as a replacement for the verse number:   [[3|bible:John 3:3]]
3. Bible text will need to be marked-off like this:  {{field-on:Bible}}Text text text.{{field-off:Bible}}
3. You'll need to use Type:Bible in the Personal Book Tool, and also denote the Language. The Language specification is only related to library metadata, so it isn't related to language-marking of the text itself (for purposes of dictionaries, etc.).

I have done a couple of PB bibles, one of which I can share here as an example. But before I do that, let's try to save you a lot of work with some questions:

• Are you sure the bible you want is not available in Logos? (probably $10-$30). Let us know what translation you're interested in. You might have missed it in a search and we can help.
• Are you needing a non-English translation? If so, tell us what that is; someone might have already posted a PB for it and we can help you look for it.

If you're certain you need to do a PB, post a three-chapter sample here and I, or someone smarter than I, can offer suggestions on how to proceed. If the technique I used on my PB bible would apply to your source document, I can post the files and provide another of my novellas (oh boy!) to explain it.

Ok, I understand now. I think you're way ahead of me. I don't know what 'Regex' is, but from your context, it is apparently some kind of text handler / parser. I assume it functions with codes that produce a desired arrangement or editing of the text based on detected patterns. In my work life I dealt with what I think is a similar product, 'Monarch', that helps the user to 'flatten' mainframe financial reports for desktop reporting in Access and Excel. When you mentioned 'coding', I assumed it was newbie-speak for 'tagging'.

What I did to produce my PB bibles was much more primitive than what I think you're referring to.