[jsword-devel] Versification and searches

Chris Burrell chris at burrell.me.uk
Fri May 30 08:51:01 MST 2014


Another thought, however, is that because of the difference in order, and
therefore the need for separate logic, we will find it hard to provide v11n
as a side-car configuration. Unless, we ask the configuration to specify
the division names as well.


On 30 May 2014 16:41, Chris Burrell <chris at burrell.me.uk> wrote:

> Hi DM
>
> Assuming you're talking about the DivisionName class in the versification
> package, from a quick glance, you're right, it's not v11n-safe. The only
> mention of Versifications is in the comments, which states that it's
> unsafe... I guess for some sections it wouldn't be too difficult to draw
> up. But others would be harder. I think this code should live in the
> Versification object. The Versification should define its sections, and
> they should map to an enum. Most of the logic around contains, etc. is
> v11n-specific.
>
> Chris
>
>
>
> On 30 May 2014 11:28, Chris Burrell <chris at burrell.me.uk> wrote:
>
>> It's perhaps a faulty assumption, but it's going to be a very common
>> assumption / pitfall for the user. The Hebrew OT isn't ordered according to
>> the Leningrad codex as far as I know.  What are we gaining by having a
>> different order anyway?
>>
>> The problem for STEP is that we allow people to search across multiple
>> versions, which suddenly means that a range becomes quite annoying because
>> it either has to mean different things depending on a 'primary' version, or
>> it has no meaning at all...
>>
>> Chris
>>
>>
>>
>> On 29 May 2014 19:38, DM Smith <dmsmith at crosswire.org> wrote:
>>
>>>
>>> On May 29, 2014, at 2:29 PM, Chris Burrell <chris at burrell.me.uk> wrote:
>>>
>>> > Hi
>>> >
>>> > Is it intentional that
>>> >
>>> > a- of the two orders of the OT in the Leningrad codex, we opted for
>>> the one that places Nehemiah as the last book
>>>
>>> We followed SWORD on the order. I presume that it was intentional.
>>>
>>> >
>>> > b- when you now do searches across what most people consider to be the
>>> Old Testament (Gen-Mal), if you're searching the OSHB you don't end up the
>>> entire canon.
>>>
>>> This is expected. It is a faulty assumption of the user. The same is
>>> true of any other OT having a different book order.
>>>
>>> There's a class in the versification package that should be able to
>>> produce a proper range for the selection of the Old Testament. IIRC, it
>>> does not work as it presumes a KJV ordering. The idea behind the class is
>>> to allow the application to have pre-defined ranges. E.g. OT, NT, Whole
>>> Bible, Prophets, Wisdom, Pauline Letters, Gospels, .....
>>>
>>> The other question is what constitutes the "canon." Some orderings have
>>> DC material mixed in. The range Gen-Mal is no longer meaningful if one
>>> wants to exclude the DC.
>>>
>>> I think that when one asks the application for the OT that they don't
>>> also get DC. If they want DC they should ask for it explicitly.
>>>
>>> >
>>> > Chris
>>> > _______________________________________________
>>> > jsword-devel mailing list
>>> > jsword-devel at crosswire.org
>>> > http://www.crosswire.org/mailman/listinfo/jsword-devel
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20140530/360cb836/attachment-0001.html>


More information about the jsword-devel mailing list