[sword-devel] Turkish module

[DM Smith]

Greg Hellings wrote:

> This might be a bit naive on my part, but is there a mechanism in the 
> Sword library that will tell the front-end that the presented text 
> covers multiple verses?  If I set a VerseKey to Genesis 1:2 is there a 
> way to retrieve where that entry begins and ends?  For example, if the 
> OSIS entry spans from verses one to three, is there a way for the 
> front end to determine that from the VerseKey?  Can it call and ask 
> beginKey() and endKey() or some such thing where the returned values 
> are 1 and 3, even though the program asked for verse 2?  I don't 
> remember seeing anything like that in the documentation, but if there 
> is such an entry, then that would simplify the application's 
> programming end of the representation.

A Sword module has an index of fixed size entries, one for each verse in 
the KJV versification scheme. Each entry is essentially an offset and 
length in another file. Because one can mathematically compute the 
location of an entry from the verse reference, one can seek directly to 
that location and read the entry. From looking at a single entry in the 
index, it is impossible to know whether it refers to a single verse or 
passage.

I think it would be simple enough to look forward and back in the index 
to see if the entry refers to a passage. But this may be "costly" for 
the average case as it would not be typical for an entry to be part of a 
passage rather than a single verse. I don't think this is the right 
solution.

Another solution would be to change the structure of the index, which 
would break current code. I don't think this is good either.

Since we have put a stake in the ground that OSIS is the preferred 
markup, I think that we can leverage OSIS  markup. (I.e. for non-OSIS 
modules that have the problem, their solution would be to migrate to 
OSIS) I think it would be better for OSIS modules to contain the verse 
element(s) to carry such information. That is the text retrieved from 
the Sword module would look like one or the other of:
<verse osisID="gen.1.1 gen.1.2" n="1-2">In the beginning....</verse>
or (more preferably)
<verse osisID="gen.1.1 gen.1.2" sID="gen.1.1" n="1-2"/>In the 
beginning...<verse eID="gen.1.1"/>

>
> --Greg
>
> On 1/16/06, *DM Smith* <dmsmith555 at yahoo.com 
> <mailto:dmsmith555 at yahoo.com>> wrote:
>
>     I have entered an issue into Jira against BibleCS. Here is the text I
>     entered:
>
>     When two or more verses are marked in OSIS with a single verse
>     tag, such
>     as <verse osisID="gen.1.1 gen.1.2" n="1,2">...</verse> the
>     rendering of
>     the text by any client should indicate both 1 and 2. Of course part of
>     the problem is that osis2mod strips the verse elements and
>     presents just
>     the content.
>
>     Example
>     1,2 In the beginning....
>     or
>     1-2 In the beginning....
>     or
>     whatever.
>
>     It might be acceptable to require and show the content of the n
>     attribute. Or perhaps show the content of n if present, otherwise
>     use a
>     programmatic form.
>
>
>     vkaehne at doctors.org.uk <mailto:vkaehne at doctors.org.uk> wrote:
>     >> I'd always thought that OK - yes - that is what it does.  I
>     suppose it
>     >> might be a slight improvement if it put out a verse range - but
>     it's
>     >> never been an issue ass far as I am concerned.
>     >>
>     >>
>     > I disagree. The BibleCS and Bibletime version of presenting
>     things could create serious problems when dealing with Muslims -
>     One of the constant features of Islamic attack against the truth
>     of the gospel is the claim that the Bible is not complete.
>     >
>     > This might sound daft to you, but I would have real hesitation
>     to show e.g. the Turkish module to a new Turkish believer - who
>     would then be tempted to think  things have been cut. Logic may
>     well be bypassed at such a moment. (This applies both to the
>     previous problem of poor encoding and to the presentational
>     problem of BibleCS and BibleTime.) Gnomesowrd's version of showing
>     linked verses is just plain ugly - but not half as damaging.
>     >
>     > Peter
>     >
>     >
>     >
>     ________________________________________________________________________
>     > National Patient Safety Agency - supporting Doctors.net.uk
>     <http://Doctors.net.uk> members in safe practice.
>     > http://www.doctors.net.uk/NPSA
>     >
>     _______________________________________________________________________
>     >
>     >
>     > _______________________________________________
>     > sword-devel mailing list: sword-devel at crosswire.org
>     <mailto:sword-devel at crosswire.org>
>     > http://www.crosswire.org/mailman/listinfo/sword-devel
>     <http://www.crosswire.org/mailman/listinfo/sword-devel>
>     > Instructions to unsubscribe/change your settings at above page
>     >
>     >
>     >
>
>     _______________________________________________
>     sword-devel mailing list: sword-devel at crosswire.org
>     <mailto:sword-devel at crosswire.org>
>     http://www.crosswire.org/mailman/listinfo/sword-devel
>     Instructions to unsubscribe/change your settings at above page
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>sword-devel mailing list: sword-devel at crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel
>Instructions to unsubscribe/change your settings at above page
>