djortley at gmail.com
Mon Jan 28 11:23:35 MST 2008
Correct me if I'm wrong, but wasn't the idea to create a virtual class
based off of Versekey that would look like a verse key to the various
front ends (aside from Bible Desktop and the Firefox extension that's
being developed right now) so nobody had to change their code?
Also, with regard to Pham's comment about the Catholic version of Sword,
I have that new cannon.h file, but it unfortunately breaks compatibility
with all other modules. In my opinion, I think it would be a good idea
to maybe tack the deuterocanon onto the end of the current bible modules
and modify canon.h to be able to handle those extra books after all the
rest. If done, I would also highly recommend we look at the canons of
the various Orthodox and Jewish groups out there as well as Roman Catholic.
I do not propose that as a solution for dynamic versification, nor as a
good open solution for all of the possibilities in books that are out
there, but it would be a good, backward compatible band aid to the issue
of missing books (missing for those of use who consider these books
canon, not missing for others.)
Chris Little wrote:
> On Jan 28, 2008, at 9:48 AM, Martin Gruner wrote:
>>>> For bibles? Does that mean they will be stored as Genbooks in
>>>> future, at
>>>> least if a non-KJV versification scheme is used?
>>> That is what I understand.
>> I am not sure I like this. Isn't VerseKey etc. prepared to work with
>> versification, only canon.h fixed the index values to save space in
>> the data
>> files? Bibles should still be offered as Bibles, regardless of the
>> impl in
>> the background.
> The underlying storage & indexing of Bibles will use something akin to
> the RawGenBook driver and TreeKeys. The work that needs to be done yet
> is to make something like the DRCgb that I just posted appear and act
> like a Bible within a frontend without requiring much major work by
> frontend developers.
> You would still be able to give the engine a plain language verse
> reference like "Genesis 1:8-12" and the engine will return the text it
> finds in Treekeys /Gen/1/8 through /Gen/1/12.
> Don't get hung up on the implementation. The API should hide all of
> the complexities (to the extent possible). VerseKeys could handle
> differing versifications, provided they were simplistic versifications
> that never had out-of-order verse numbers. I'm not even sure we could
> change the ordering of books using VerseKeys.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel