Personal Book (Bible)

I have been rummaging through the Help and through these posts but I am still having trouble.

I want to create a personal translation. I will use the beginning of Philemon as my example. I want it to look like this-

Philemon

Chapter 1

Greeting

1 From Paul, held prisoner for his allegiance to Christ Jesus, and from your brother Timothy. We send our greetings to Philemon, that well-loved fellow worker of ours, 2 and to Apphia our sister in the faith, to Archippus our comrade-in-arms, as well as to the congregation which meets at your house, Philemon. 3 May grace and peace...

======================

Philemon I formatted the Book Name as Heading 1 in the Word docx -seems to work

Chapter 1 I formatted the Chapter header as Heading 2 in the Word docx -seems to work

Greeting I formatted the pericope as centered italic but I don't know which tag(s) to surround it with. Perhaps format Heading 3 / 4.

I can't figure what tags to wrap the verse numbers in. I figure milestones, headings, headwords and hyperlinks are not appropriate because verse numbers are neither headings nor jumpto instructions. And I think BibleText seems to be for quoting bible within other words. So I figure it must be BibleMilestones but the syntax doesn't seem to fit. That syntax does not seem to offer a way to surround the verse number.

Additionally, the make book process causes this passage "...your house, Philemon. 3 May grace" to be recognized as some sort of crossreference, in this case to non-existent chapter 3. How do I stop it?

Is there a tutorial/reference specifically aimed at creating a bible rather than a book or article?

Find more posts tagged with

Comments

NB.Mick

Len,

making a bible is a complex task. I'd suggest you read through the wiki page on Personal Books for general reference and then look into threads in the Files forum where making bibles is discussed, such as this thread.

If I were you, I'd take one of the existing Bible PBs as a template, such as shared here or here.

Hope this helps,

Mick

NetworkGeek

https://community.logos.com/discussion/comment/408089#Comment_408089

Here is another good thread, where Mark Barnes uploaded some public domain Bibles in docx format that you can take a look at.

Thomas B.

https://community.logos.com/discussion/comment/408094#Comment_408094

It would/could have been so much easier which a decent XML schema to tag the relevant bits and pieces. Instead, formatting is "magically" derived from Word style template. I have given up on this approach for anything but the most straightforward texts.

tom

https://community.logos.com/discussion/comment/408789#Comment_408789

It would/could have been so much easier which a decent XML schema to tag the relevant bits and pieces. Instead, formatting is "magically" derived from Word style template. I have given up on this approach for anything but the most straightforward texts.

Yes and no. The problem is that most people do not know XML.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/408789#Comment_408789

Instead, formatting is "magically" derived from Word style template.

The "magic" transformation uses XML => http://www.dq.winsila.com/tips-tricks/exploring-the-insides-of-a-docx-word-document.html

Philemon 1:1 in document.xml from thread => http://community.logos.com/forums/t/42950.aspx has a Heading1 style for the book plus tagging for Bible text and verse numbers using KJV versification:

<w:pPr><w:pStyle w:val="Heading1"/></w:pPr><w:r><w:t>[[@BibleKJV:Pm]]The Epistle of Paul to Philemon</w:t></w:r></w:p><w:p w:rsidR="00557427" w:rsidRDefault="00557427" w:rsidP="00557427"><w:r><w:t xml:space="preserve">{{bible-on}}[[@BibleKJV:Pm1:1]]Paul, a prisoner of Christ Jesus, and Timothy our brother, to Philemon our beloved and fellow-worker, [[@BibleKJV:Pm1:2]]

In Word 2010 with XML tags hidden from view, the text looks like:

[[@BibleKJV:Pm]]The Epistle of Paul to Philemon

@{{bible-on}}[[@BibleKJV:Pm1:1]]Paul, a prisoner of Christ Jesus, and Timothy our brother, to Philemon our beloved and fellow-worker, [[@BibleKJV:Pm1:2]]

Keep Smiling [:)]

Thomas B.

https://community.logos.com/discussion/comment/409374#Comment_409374

I am know and I agree. And yet, it requires an awful lot of second-guessing the styles, rather than exact and predictable control. You have to learn a new language anyway (to tag the various fields), so why not go the last mile too? Why not support USFM? Or OSIS?

Len Browne

https://community.logos.com/discussion/comment/409374#Comment_409374

My knowledge of XML needs upgrading in so far as it relates to docx. oh, well, one day.

Thanks everyone for your input and links. I have decided to use the following formatting pattern and thus far it seems to work.

[[@Bible:Phm 1:1]] [[1:1|bible:Phm 1:1]] From Paul, ...ours, [[@Bible:Phm 1:2]] [[2|bible:Phm 1:2]] to Apphia ...

This results in
1:1 From Paul, ... ours, 2 to Apphia ...

Now when I hover over the (chapte/)verse number, I see a popup of the verse from my preferred bible. Handy. And of course, clicking will open my preferred bible to that place.

The mis-recognized reference to Philemon 3 is no longer a problem. The tagging before the 3 seems to make that ok.

One thing, though. I havent seen before any mention of @BibleKJV as opposed t the simpler @Bible. The implication is that KJV has different versification. That surprises me. Is it true and how is it different?

NB.Mick

https://community.logos.com/discussion/comment/411163#Comment_411163

One thing, though. I havent seen before any mention of @BibleKJV as opposed t the simpler @Bible. The implication is that KJV has different versification. That surprises me. Is it true and how is it different?

Nearly all bibles have different versification in some obscure places, thus Logos has an individual versification datatype for nearly every bible. It shouldn't matter in most cases, but you should be sure of which you want to follow e.g. in Psalms. The various versifications allow Logos to show the same verse regardless of whether it is numbered 29 in one bible or 30 in the next.

Dave Hooton

https://community.logos.com/discussion/comment/411219#Comment_411219

One thing, though. I havent seen before any mention of @BibleKJV as opposed t the simpler @Bible. The implication is that KJV has different versification. That surprises me. Is it true and how is it different?

Nearly all bibles have different versification in some obscure places, thus Logos has an individual versification datatype for nearly every bible. It shouldn't matter in most cases, but you should be sure of which you want to follow e.g. in Psalms. The various versifications allow Logos to show the same verse regardless of whether it is numbered 29 in one bible or 30 in the next.

When you use a modern bible the NT is usually based on a Greek "critical" text whereas KJV is based on a much older text. One result is that the KJV recognises verses that modern bibles do not e.g. Ro 16:24 is omitted in the Critical text and most modern bibles, except the LEB. This is one reason for bible versification schemes. Because of these you can type a reference like Ro 16:24 into the ESV bible but it will result in a reference to Ro 16:23; the nearest verse. Ro 16:25-27 is recognised by most modern bibles (without annotation) but omitted from the LEB!

Whilst the story of Jn 7:53 - 8:11 is not recognised in the Critical text it is included in most modern bibles with an annotation like "The Earliest manuscripts do not include 7:53-8:11" and is therefore included in their versification scheme.

Dave Hooton

https://community.logos.com/discussion/comment/411163#Comment_411163

[[@Bible:Phm 1:1]] [[1:1|bible:Phm 1:1]]

Whilst the pipe symbol | may still be recognised you should use >> with labels i.e. [[1.1 >> Phm 1:!]]

Randy W. Sims

https://community.logos.com/discussion/comment/411289#Comment_411289

Ro 16:24 is omitted in the Critical text and most modern bibles... you can type a reference like Ro 16:24 into the ESV bible but it will result in a reference to Ro 16:23

OT Observation: Reftagger doesn't seem to handle that well. Says "Loading" for a bit. Then displays an error.