chrislit at crosswire.org
Mon Sep 20 10:23:12 MST 2010
The Jerusalem Bible should be fairly straightforward, from your
description. We just need to pick a versification and use it,
preferrably the one that looks like their favored versification. All
v11ns should be encoded in the OSIS doc, but the JB v11n should precede
others. If "2:7, 1:3" indicates the verse number in JB and NRSV,
respectively, it would be encoded as osisID="Bible.JB:Esth.2.7
Bible.NRSV:Esth.1.3". The lettered subverses are a little simpler: 1:2b
is just osisID="Bible.JB:Esth.1.2!b".
For Sword's importer, until some day in the distant future when we
support multiple versifications within a single document, we just want
to read the JB v11n references, and ignore the NRSV ones. Handling of
subverses should already be supported by osis2mod.
Lettered chapter numbers are a bit of a different challenge. They aren't
supported by the SWText driver. They are supported by SWGenBook, but
that's not well supported for Bibles yet.
Additionally, there's the problem of chapters being interrupted by other
chapters and then resumed (sometimes much later) in the book. I don't
believe there is currently any easy solution to that problem.
My recollection of constructing a GenBook is a bit hazy, but I believe
that if you try to write the keys:
1:1, 1:2, 1:3, A:1, A:2, A:3, 1:4, 1:5
You'll end up with 1:4 and 1:5 as children of the first chapter 1, not a
second chapter 1 that follows chapter A. In other words:
not the desired:
I don't think we can solve this problem, because my recollection is that
two child nodes of a single parent cannot have the same name in our
All that said, in every case of this versification that I've seen, the
lettered "chapters" aren't in fact chapters. They are termed
"additions". So Chapter 11 consists of the last verse of Addition F
(Esth.11.1, the last verse of Greek Esther) and the first part of
addition A (Esth.11.2-Esth.11.12). It's hard to explain the NRSV v11n of
Greek Esther, but I would recommend grabbing one of the ecumenical
NRSVAs, like the New Oxford Annotated Study Bible, if you want to see
the worst-case scenario of versification.
On 9/11/2010 12:15 PM, Greg Hellings wrote:
> I have brought this up before, relating it to the Jerusalem Bible,
> which does something similar. Instead of using A, B, C, etc, they
> simply will number a verse as "2:7, 1:3" to reflect both popular types
> of versification or they will go "1:1, 1:2, 1:2a, 1:2b, 1:2c, 1:3,
> 1:4" to indicate additional material present in Greek Esther or
> No one has given me a solid answer as to how that would be encoded. I
> don't even know if the engine has support for chapter "numbers" that
> are represented as letters. It would be easiest to use a General Book
> driver which allows arbitrary key values, if the GenBook-VerseKey
> bridge was completed. I don't know that it is, as I haven't heard
> anything about it for some time.
> On Sat, Sep 11, 2010 at 2:09 PM, Peter von Kaehne<refdoc at gmx.net> wrote:
>> How do you deal with a versification which is using two separate chapter
>> counters in a book which aun in an interspersed way?
>> 1, 2, 3, ...
>> A, B, C, ..
>> This is to deal with Greek and Hebrew Esther and Daniel.
>> To make it more complicated, some "numbered" chapters start and finish
>> with a "lettered" chapter interspersed.
>> 1:1, 1:2, 1:3, A:1, A:2, A:3, 1:4, 1:5... You get my drift.
>> I would rather have it right, but I would rather have it working too.
>> And that bugs me.
>> This is obviously the Portuguese Bible.
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel