I have a few questions (that are born more out of ignorance than anything else..like most of my thoughts.)<br><br>Is the idea that is being talked about to create a new VerseKey that takes an input that is assumed to be the versification of a KJV verse and translate that to what's appropriate for any module type so the reference will always be pertinent?
<br><br>If so, then could I give a suggestion that VerseKey be reworked to NOT do that and to just provide pure access to whatever the module has and then have a reversifier (new word:) ) object that somehow handles the versification?
<br><br>Maybe, to avoid breaking everybody else's code, make VerseKey the reversifier and create a new object to access verses in their pure state, like a PureKey object or something? There are many reasons why someone would want to have access to a non-reversified bible, and I'm sure I don't need to come up with examples.
<br><br>I don't know how hard or wrong of a thing it would be to do that, but from what I can tell, I think that its not too poor of an idea. Of course, I may have just rehashed what everyone else was thinking, in which case ignore me (though tell me before ignoring me:) )
<br><br>I'm trying to stimulate conversation in this area to see what people think. I'm looking for criticisms or suggestions. From what I understand, there's no momentum and this is a fairly open problem.<br>
<br>Also, one last question out of curiosity, are references to the NKJV made because, aside from the non-Protestant books, its of the same versification as the KJV?<br><br>-DJ<br><br><br><div><span class="gmail_quote">On 3/10/07,
<b class="gmail_sendername">Troy A. Griffitts</b> <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sorry, wanted to change the subject of this thread, and also wanted to<br>correct a technical typo below:<br><br>-SWORD Bibles use). The new TreeKey subclass will be implemented to<br><br>+SWORD Bibles use). The new VerseKey subclass will be implemented to
<br><br><br>Troy A. Griffitts wrote:<br>> Jeremy,<br>> Thanks for the great work you guys do over at Biola and for your<br>> encouragement and offer to help with ideas.<br>><br>> Sean,<br>> Yes, this would allow deuterocanonical books.
<br>><br>> Greg,<br>> Yes, you have the current plan correctly outlined. Work has been<br>> started.The goal is to take a module like LXXM:<br>><br>> <a href="http://crosswire.org/study/bookdisplay.jsp?mod=LXXM&gbsEntry=%2FPsSol%2F18%2F1#cv">
http://crosswire.org/study/bookdisplay.jsp?mod=LXXM&gbsEntry=%2FPsSol%2F18%2F1#cv</a><br>><br>> which is currently imported as a SWORD General Book (General Books use a<br>> TreeKey index, as you can see from the left navigation) and to make it
<br>> accessible via a new specialized VerseKey descendant (VerseKey is what<br>> SWORD Bibles use). The new TreeKey subclass will be implemented to<br>> merely walk the existing TreeKey index of the General Book module format
<br>> to get it's data (books, chapter max, verse max, etc) and will position<br>> the TreeKey to the appropriate node when it is positioned to, say, "John<br>> 3:16".<br>><br>> I started the work a really long time ago and think I merely got the
<br>> classes in place. I can't remember actually. I remember it was more<br>> ugly than I thought. Anyone is welcome to have a look and try to<br>> understand where I was headed. If you have questions, I'll try to answer.
<br>><br>> I would also love to have this completed but just haven't had the time<br>> or motivation to jump back in. Any help would be greatly appreciated.<br>><br>> A few good places to start looking:
<br>><br>> The new VerseTreeKey class:<br>> <a href="http://crosswire.org/svn/sword/trunk/src/keys">http://crosswire.org/svn/sword/trunk/src/keys</a><br>><br>> The genbook driver (search for 'verse'):
<br>> <a href="http://crosswire.org/svn/sword/trunk/src/modules/genbook/rawgenbook/">http://crosswire.org/svn/sword/trunk/src/modules/genbook/rawgenbook/</a><br>><br>> The SWMgr class looks for a new property in a module's .conf file
<br>> (search for "KeyType"):<br>> <a href="http://crosswire.org/svn/sword/trunk/src/mgr/">http://crosswire.org/svn/sword/trunk/src/mgr/</a><br>><br>> -Troy.<br>><br>><br>> Greg Hellings wrote:
<br>><br>>> I agree with Jeremy. This seems like an ideal time to surge forward<br>>> in the alternate versification planning. Last I had heard there were<br>>> already significant plans/work in place already on this, is that true?
<br>>> I thought the plan was to use a TreeKey with an interface that<br>>> allowed existing use of the VerseKey interface to automatically map to<br>>> the proper portion of the tree for selected verses to allow current
<br>>> clients to continue working with the library. Is that approximately<br>>> right?<br>>><br>>> How much work has been done on it? What remains to tackle?<br>>><br>>> --Greg<br>>>
<br>>> On 3/10/07, Jeremy Brown <<a href="mailto:jeremy.brown@biola.edu">jeremy.brown@biola.edu</a>> wrote:<br>>><br>>><br>>>> That is really great. I don't post here much (ever?) but I am appreciative
<br>>>> of the work Crosswire does.<br>>>><br>>>> I have a question, in the face of the coming onslaught of Bible<br>>>> translations. It regards the versification schemes. I know people always
<br>>>> ask about that, and it is on the to-do list. But I wonder if now would be<br>>>> a great time to do something about the problem. Right now (if I'm wrong,<br>>>> forgive me), Sword seems to take non-KJV versification schemes and squish
<br>>>> them into KJV chapter/verse format. I have tried to work up an alternate<br>>>> solution and basically I know that there is no perfect answer - every<br>>>> solution has its trade offs. However, since has an enormous number of
<br>>>> translations, and probably many of those don't fit the KJV versification<br>>>> model (they may follow the model of the national language where they were<br>>>> translated, or merge multiple verses together
e.g. verse 1-7), it seems<br>>>> like if you can plan a strategy and deal with the issue now, you won't<br>>>> have to code all those translations once, and then recode them again when<br>>>> you do make the change.
<br>>>><br>>>> I currently have about 30-40 Bibles/testaments that are mapped/partially<br>>>> mapped to the verse system in the NRSVA. The original versification is<br>>>> preserved in the database, but also the matching verse number in the
<br>>>> NRSVA. There are some things I would have done differently, that I now<br>>>> know about. If you are interested in hearing more from me about this, I'd<br>>>> be happy to share. You may already have some ideas in the works, I don't
<br>>>> know.<br>>>><br>>>> Keep up the good work!<br>>>><br>>>> Jeremy<br>>>><br>>>> <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
on Saturday, March 10, 2007 at 11:00 AM -0800<br>>>> wrote:<br>>>><br>>>><br>>>>> With great joy, I would like to officially announce that CrossWire and<br>>>>> SIL have entered into an agreement which allows us to distribute,
<br>>>>> royalty free, SIL Bible translations, anywhere in the world, for an<br>>>>> initial 5 year trial period.<br>>>>><br>>>>> This is huge answer to prayer.<br>>>>>
<br>>>>> A number of years ago, when we first started working with SIL/Wycliffe,<br>>>>> we had talks about publishing their Scripture translations. They<br>>>>> proceeded to tell us of the internal struggles between those who wished
<br>>>>> to release their work for free, and others who held that the<br>>>>> organization needed to continue to charge royalties for their work to<br>>>>> allow them to continue work into the future.
<br>>>>><br>>>>> About a year ago Wycliffe started a project to use our software to<br>>>>> publish their Bibles online, themselves.<br>>>>><br>>>>> This contract allows CrossWire to distribute all of their Bibles freely
<br>>>>> in all of our software!<br>>>>><br>>>>> The papers came officially signed in the mail today. We are hoping to<br>>>>> have data files start coming in over the next couple weeks. We could
<br>>>>> really use help in many new areas as we start to bring these great<br>>>>> resources online.<br>>>>><br>>>>><br>>>> _______________________________________________
<br>>>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>>>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel
</a><br>>>> Instructions to unsubscribe/change your settings at above page<br>>>><br>>>><br>>>><br>>> _______________________________________________<br>>> sword-devel mailing list:
<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>>> Instructions to unsubscribe/change your settings at above page
<br>>><br>>><br>><br>><br>> _______________________________________________<br>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">
http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>> Instructions to unsubscribe/change your settings at above page<br>><br><br><br>_______________________________________________<br>sword-devel mailing list:
<a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page
<br></blockquote></div><br>