Personal Bible Book file preparation
I am in the process of preparing a personal book or more specifically a personal bible to add to my Logos Library.
I have a few questions about the process.
1) In the first chapter of every book, should I add the first verse number (1)?
2) Is it a good idea to have the book names assigned ‘heading 1’ and the chapter numbers assigned ‘heading 2’?
3) Should I add the milestone, [[@Bible:John3:16]], before or after each verse number?
4) Should I use a two-letter abbreviation for the book name or the full name in the milestones?
5) If I should use the two-letter abbreviations would you please send them to me?
6) Are milestones the only required syntax?
7) Should my file have a title page or can I start with Genesis 1:1?
8) Should my bible file contain no page breaks?
9) What dimensions or size should my image file be?
10) When I get a Bible quote using Logos it shows the bible version, ie. John 3:16(KJV). How do I get my personal bible to show my personal bible (ABBR.)?
Thank you very much in advance for your assistance.
Comments
-
Hi Jacques:
See if this helps:
- It's up to you. Most that I see omit it, but that appears to be tradition. But you will need to put the milestone.
- Yes to both; it will make your Table of Contents pane much more useful. If you have pericope (or section) headings, it would be a nice touch to make them Heading 3.
- It doesn't matter.
- I always use the full name, but I usually devise some kind of automation to insert them, so the length isn't a practical matter. Here's the link to the official Logos name reckoning: https://support.logos.com/hc/en-us/articles/360021229852-Bible-Book-Abbreviations
- See 4.
- No. To make your bible behave more like a Logos edition, you'll need to mark off the actual bible text with field-on / field-off tagging. That would exclude CV numbers, pericope headings, etc. This will make your bible useful in Bible searches, Text Comparison, Copy Bible Verses, and other functions. That tagging will look like this:
[[@Bible:Genesis 1:1]][[1|bible:Genesis 1:1]] ¶ {{field-on:Bible}}In the beginning God created the heavens and the earth;{{field-off:Bible}}
[[@Bible:Genesis 1:2]][[2|bible:Genesis 1:2]] {{field-on:Bible}}and the earth being without form and empty, and darkness on the face of the deep, and the Spirit of God moving gently on the face of the waters,{{field-off:Bible}} - Note the tagging that are following the @Bible milestones. Those will cause preferred bible mouse-over popups for verse numbers; they aren't necessary, but I like having them.
- Also note the paragraph mark. Those help to preserve the translator's decisions if you are formatting your bible 'one-verse-per-line'.
- For bible functionality, that's cosmetic and up to you.
- That doesn't matter. The PB compiler will ignore page breaks and omit large areas of whitespace.
- I'm not sure if that's an issue, but if it is, I don't know.
- The compiled resource will have the name you specified in the PB Tool. I think when Logos abbreviates it, it will do its best to make some initials. But once the file is compiled, you can see it in the Library and specify (in the Information pane) the 'short name' you want.
Here is the Wiki page for Personal Books that you'll want to review before doing a lot of work: https://wiki.logos.com/Personal_Books .
[Edited #1 with additional sentence. Edited #3 because I didn't read your question carefully.]
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0 -
Thank you Robert M. Warren!
This is very useful.Also, it is interesting that my brother, Robert, was married to a Warren. He died a few years ago.Jacques Gauvin0 -
Hi Robert,
About #6, your note 1. talks about popups, can you show me the syntax to avoid popups? I generally do not like popups.
0 -
Sure:
[[@Bible:Genesis 1:1]] 1 ¶ {{field-on:Bible}}In the beginning God created the heavens and the earth;{{field-off:Bible}}
[[@Bible:Genesis 1:2]] 2 {{field-on:Bible}}and the earth being without form and empty, and darkness on the face of the deep, and the Spirit of God moving gently on the face of the waters,{{field-off:Bible}}macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0 -
While doing this step a Word popup said that I should delete some text as my file was now too large to save. Do you have any idea why this happened and how to get around the problem? My file appears to be less than 2 MB and the capacity of Word is around 32 MB, as far as I can determine. Is it possible that I saved during a procedure when I should have saved after the procedure had been completed?
0 -
Hi Jacques:
I've not heard of that Word issue before. I know sometimes Word (but more often, Excel) will run into a problem and not know whether to cry or play tennis, so it throws some inappropriate dialog up and hopes for the best. If you save your document often, maybe you could post a screen-shot of what you and Word were seeing when the dialog first came up. Maybe some of the Word wizards on the Forum will see this and have an idea.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0 -
Hi Robert, (or anyone else who can help)
I was able to Build my book without errors and to upload it. It works very well. However, I had many warnings. Here is a list of each type of warning I had except the one that I was able to resolve myself. I wonder if you could help me with these?
[Warning] Document contains Hebrew characters (“א”) that have not been tagged with a language code; they may not display in the proper order.[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.4.5.2
[Warning] closing field bible that is already closed.
[Warning] Unknown class name 'HebrewText'
[Warning] opening field bible that is already open.
Thanks!
0
