refdoc at gmx.net
Sun Jan 27 16:50:20 MST 2008
> Seeing as the hard coded versification scheme seems to be limiting many
> areas of growth for Sword and it's possible uses, I was wondering if a
> new versification method could be placed as a high priority.
> Just a thought:
> Is it possible to have the Sword library parse a text file with
> different versifications defined in it? If so, then a new line could be
> put in the .conf files stating which versification was used. I'm also
> thinking that parsing versification from a text file would probably be
> incredibly slow. I just thought that it could be a way that anyone
> could create a new versification for any use they needed.
I think this suggestion has been around for a while and was always
considered to be a good one. But I could not programme my way out a wet
> Daniel Blake
> The lurker
> Chris Little wrote:
>> Greg Hellings wrote:
>>> The issue here is that the Vulgate has some Psalms which the KJV has
>>> split that it lumps together and others which the KJV lumps together
>>> split up, and there's an additional Psalm as well. It's very similar
>>> to the situation in which Esther and Daniel find themselves in the
>>> Catholic form the canon.
>> Ah, ok, then it's just another part of the versification issue. There's
>> nothing particular about Vulgate versification here and it's not
>> remotely limited to Psalms. The KJV & Vulgate begin to diverge in
>> versification back in Exodus, to my recollection.
>> There's not a _good_ solution to the problem right now, but if you just
>> encode the OSIS correctly, osis2mod will do a fair job of importing the
>> text. No text is lost, but non-KJV verses appear contiguous with the
>> preceding KJV verse.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel