The import tools, including osis2mod, have a very simple algorithm for
handling verses that they does not recognize as canonical KJV verses.
They attach them to the previous valid KJV verse, following an
identification of the verse number in the native (non-KJV) versification
scheme.
So:
1) No information is ever lost.
2) If you query a non-KJV verse, the prior valid KJV verse will be
returned, meaning you will still get the content you queried, just with
some other stuff presumably preceding it.
3) No re-versification or versification normalization/standardization is
occurring. If it were, you'd see verses from non-KJV reference schemes
being placed in the verse with the same content in the KJV. This is (for
better or worse, since it does have its advantages) the kind of thing
you find in some OLB modules.
--Chris
[EMAIL PROTECTED] wrote:
Hi,
I also have several issues with osis2mod, and I was getting ready to
post. The fact is that there are several versification schemes for both
Old and New Testaments. I was having a similar problem with
re-versification in Tischendorf's Greek New Testament. It has John
1:52, because an earlier verse is sub-divided. But it also has 3John 15
and Rev 12:18, which agrees with UBS 4.
How can we get osis2mod to recognize true variations in versification,
and not "standardize" everything?
Peace,
David
------------------------------------------------------------------------
_______________________________________________
sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
