On 08/29/2015 10:42 AM, Karl Kleinpaste wrote:
On 08/28/2015 10:18 PM, Kahunapule Michael Johnson wrote:

At least as importantly, how would Joe Average distinguish them?

Good question. That kind of depends on how much information is presented to Joe Average.
My point in asking is that their mere presence duplicates these modules, creating what amounts to uncertainty and competition where none should exist.  Is not Crosswire itself the source of these modules?

That you have named one of them peculiarly (Crosswire's KJVA is essentially eBible's KJVD) adds to the confusion.


I'm going to dispose of the following modules on the eBible.org repository in hopes of reducing confusion without really taking anything of value away from the public:
engRVX2012 - doesn't really add anything beyond what engRV1895 and engWEB2015 provide. I'd rather remove it than explain it.
engUKWEB2015 - proper subset of engWEBBE2015 (omits Deuterocanon/Apocrypha)
engWEBc2015 - proper subset of engWEB2015 (omits books not in the Roman Catholic Bible)
engKJV2006 - redundant with the KJV in the main repository; subset of engKJV1769

For the subset books, I would rather see filter options on searching and displaying texts than make multiple modules from the same source. I want to make these modules and this software useful for Christians from a variety of church traditions while trying to stay somewhat neutral on how to treat the books beyond the 66-book canon. Attitudes towards those books are wildly diverse, so I don't know how viable that strategy is. I may be convinced to backtrack on that, later, but for now, this seems too hard to deal with in a short module name, and not really worth the effort.

Regarding the naming of the KJV with Apocrypha: I try to make my abbreviations mesh not only with Crosswire, but even more importantly, with the American Bible Society's abbreviations. For them, KJVA is the Americanized King James Version. Sigh.

For now, I'm leaving engKJV1769 in the eBible.org repository until such time as DM and I come up with a better idea together. I've been distributing the KJV from eBible.org, and before that from a computer bulletin board, dating back to before the Sword Project began. I have done some reconciliation with DM's copy on Sword from time to time.  I'm using the KJV as a markup test, as well as an additional output format for the KJV. Also, there are some variations in the Apocrypha between the two copies, plus some typo reports pending to implement. I'll start sharing those with DM as I get them. If David's analysis of the text differences in the 66 books of the KJV canon is correct, there are only a handful of variations where my printed copy and DM's differ, so we could just overwrite mine with DM's latest KJV, give or take markup issues. I'm sure we can figure out a way to collaborate effectively, but it may take a bit of time to figure it out, and for me to write some software to import a specific subset of OSIS. (I have resisted making a general OSIS importer, because that is very difficult, and nobody has ever done it to my knowledge, but it shouldn't be hard to ingest just that tiny part of what OSIS allows that the KJV master copy is in.)


--

Aloha,
Kahunapule Michael Johnson

MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143

USA
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
_______________________________________________
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

Reply via email to