We have many modules whose scope does not match the versification. E.g. NT
Bibles, translations with a book or two. Having an adaptive list of books based
upon the modules being viewed is the way to go.
Chris Burrell added some code to JSword that allows for the quick determination
of whether a verse is present in a module. He is using this in STEP to prune
the v11n to only those books, chapters and verses that are actually present. On
old slow hardware he reported that it is very fast to analyze an entire module.
Given that C++ is even faster than Java, I'd suggest such a mechanism for SWORD
lib.
So, I concur with Chris L but for different reasons.
In Him,
DM
On May 11, 2013, at 5:28 PM, David Haslam <dfh...@googlemail.com> wrote:
> Did IBT's programmer actually know that you'd provided it during the period
> in question?
>
> It might just have been not used due to his excessive workload, or other
> factors affecting his situation.
>
> If we have Luther and German as two similar cases, why balk at SynodalP?
>
> IMHO, the argument against it is flimsy.
>
> David
>
>
>
> --
> View this message in context:
> http://sword-dev.350566.n4.nabble.com/Synodal-versification-IBT-modules-tp4652282p4652284.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> 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
