[sword-devel] KJV verse numbering is not universal.

[Jerry Hastings]

Custom BKS and CPS indexes, if found,  could also be read into the indexing 
arrays instead of using the default. As to the vpl2mod program, command 
line settings could set it to use the Sword/KJV standard, or read book, 
chapter, verse info from the vpl file, and create the custom BKS, CPS 
indexes. One could also edit the custom indexes to produce a KJV index for 
the text so KJV based commentary references would find the correct verse.

Jerry

At 01:08 PM 9/4/2000 -0600, Michael Paul Johnson wrote:
>At 10:50 AM 9/4/00 -0700, Chris Little wrote:
> >...  I'm not sure what we'll do for translations with
> >more verses in any given chapter than the KJV since SWORD would map them
> >onto verses in the following chapter, where another verse ought to exist.
>
>This is an important issue to clarify. Consider Romans 14:26 (WEB or MT), 
>which is equivalent to Romans 16:27 (KJV) or 3 John 15 (NRSV or UBS4), 
>which is equivalent to 3 John 14b (KJV). Trying to force all Bible 
>translations to use the KJV versification is a mistake, in my opinion. If 
>you must persist in this mistake, probably the only really graceful way to 
>handle it is to include all verses after the last KJV verse in a given 
>chapter as if they were an extension of the last KJV verse in that 
>chapter. That would stuff Romans 14:23-26 of the Greek Majority Text and 
>all translations based on it in Romans 14:23, for example. (The KJV puts 
>Romans 14:24-26 at the end of chapter 16, presumably because the 
>translators didn't have access to the majority of manuscripts that put 
>those verses earlier. It makes little difference in meaning or theology, 
>either way, but it is something that any good Bible study program deals 
>with gracefully.)
>
>
>_______
>
>Michael Paul Johnson
>mpj@eBible.org    http://ebible.org/mpj