Re: [sword-devel] NASB status

[Kahunapule Michael Johnson]

The Sword Project has done some pretty awesome things in open source Bible study software over the years. Taking more than 12 years to release a NASB module in any form is not one of them. 1) Yeah, it is a duplication of effort, but I have a scripted solution to turn Lockman's unique XML-like source into USFX/USFM/OSIS/etc., and have done so for 4 of their translations (NASB95, Amplified, NBLA, LBLA). 2) My scripted solution supports their entire data set (footnotes, cross references, Strong's numbers). 3) The result works with most major SWORD/JSword front ends EXCEPT that PocketSword's index generator has not been running. (I expect that to be done soon if it is going to happen at all. If it isn't, then that front end is not relevant.) Unfortunately, lacking a legal distribution outlet for those for Sword modules, I just let the output sit all by itself on my computer, where nobody can read it. Of course, I never asked them for permission for distribution on eBible.org. I just worked on those Bibles for the Digital Bible Society to put them into InScript format, because they already had permission for that. The resulting Sword modules were just a side-effect of the automation of Haiola. I plan to remedy that. Tomorrow, I plan to ask the Lockman Foundation for permission to distribute the NASB for free from eBible.org in various formats, including Sword. Please pray for favor. If they go for it, great! If not, long live the WEB, ESV, God's Word, KJV, ASV, etc.! English speakers can read the Holy Bible in Sword front ends with a reasonable choice of translations. By the way, I have good source for the NIV, HCSB, and MEV, too, also from processing DBS InScript modules. I could release them in Sword format within an hour of solid work if I had permission to do so, BUT some things are slower than we are, like getting permission from some organizations to post their copyrighted translations. Actually, I would give us better than even odds of getting permission to post the Modern English Version if we asked properly. The MEV is an update of the KJV that sticks pretty close to it, but with a little more modern English than the NKJV. Hopefully this is more constructive than just beating each other up for taking so long. This "can" will either get kicked down the road or thrown into the recycling bin, soon. On 01/06/2016 12:04 PM, Troy A. Griffitts wrote: I hesitate to even respond to this thread, as none of this kicks the can down the road, but... I believe some of the issue has to do with typical open source volunteer problems. Specifically, in this case, none of the pumpkin holders was satisfied to build on their predecessors' code. I originally made the initial co version in C++. My script is versioned in the sword-tools repo. I'm not sure what Chris did. I know DM rewrote the conversion in Java, and it sounds like Greg has again rewritten the conversion in Python. It is not a matter of perfection before release. It is a matter of basic satisfaction of the three items I have listed and we have not attainted basic satisfaction yet. Troy On January 6, 2016 2:51:55 PM MST, "Matěj Cepl" <mc...@cepl.eu> wrote: On 2016-01-06, 18:53 GMT, Troy A. Griffitts wrote: This is a commercial module to be sold by Lockman. That is a different scenario from other modules. For this module, I have reasonably asked: I didn’t like Karl’s tone last time the flamewar went around, but I have to admit he is right. Whatever you say is suspicious because of one argument: “Twelve years”. 1) That we have a scripted, reproducible way to transform their data from their pristine source to a module. Yes, what’s the problem? Whom you asked for help (e.g., I have developed completely automatic conversion of CzeCSP from one XML to OSIS, and it didn’t take me twelve years to do it)? Twelve years. 2) That we support their entire dataset which they have given us for this module (base text + footnotes / crossrefs + lexica) Yes, I have CzeCSP with footnotes, crossrefs, and notes. Twelve years. 3) That the result works generally in all major SWORD/JSword frontends. What are the problems? Where are the bugs? Where is the progress on development of the module recorded? I would be willing to buy the module, if that was required to work on it. Twelve years. It is not as simple as-- just release it and fix it later. This is to be sold by Lockman. What do you mean? I work for Red Hat. We sell software in tune of some, let's say, two billions of USD. Of course, we don’t expect it to absolutely perfect and bug-free. If there are bugs in the module, we can certainly provide a fix. Where is the alpha version, how do you plan to make QA working? Twelve years. Historically, we have had at least 4 people own this effort over the years. It is not simply that one person has sat on this and hasn't finished it for 12 years. Yes, so where are products of work of all these people? What did they do? I mean, I honestly believe that some work was done, but without some presentation of the results, how can we know what's done? Here “Twelve years” makes it even more difficult to be persuaded. I think we are close. In my mind, the current owner (Greg) simply needs to have a list of outstanding items which keep us from satisfying 1-3 and push each of them down the road until they are done. And where is that list? That is my question. I don't know what those items are. I am just concerned that we meet 1-3 before we give the data to Lockman to sell and I feel these 3 items are reasonable requests. I don't think Lockman expects the work to be ever done at this point, but that's another thing. If they do, they have my admiration (or something else). However, if you (or Lockman) expect that you will hand over finished absolutely prefect module and Lockman will never ever see you (or anybody from the Sword project) again, than I think you are sorely mistaken. Unless of course they are prepared to maintain the module themselves. After all, even NASB itself is (according to Wikipedia) in its tenth edition. Blessings, Matěj -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ 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 -- 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