Re: [sword-devel] anniversaries

2017-05-27 Thread Michael Johnson
On 01/09/2017 03:56 PM, Karl Kleinpaste wrote: > On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote: >> I'm pretty sure the Lockman Foundation is not actually interested in >> releasing the NASB on Sword. > > You misunderstand. There has been a Lockman-sanctioned NASB in progress since >

Re: [sword-devel] anniversaries

2017-01-27 Thread David Haslam
I got confirmation that the Tyndale STEP module NASB-TH is not yet released. I have more details if anyone should contact me outside this channel. David Haslam -- View this message in context: http://sword-dev.350566.n4.nabble.com/anniversaries-tp4656611p4656657.html Sent from the SWORD Dev

Re: [sword-devel] anniversaries

2017-01-24 Thread David Haslam
I suspect the STEP Bible blog posting was erroneous as regards the NASB. AFAIK, it's not one of their licensed modules distributed with a "JSword configured" unlock key. I've emailed Tyndale STEP Development for clarification. David -- View this message in context:

Re: [sword-devel] anniversaries

2017-01-24 Thread David Haslam
*STEP Bible* now has this available: New American Standard Bible (*NASB*), tagged by CrossWire for www.Lockman.org See https://stepweb.atlassian.net/wiki/pages/viewpage.action?pageId=101122055 Not sure how they made progress with that, and then with the attribution to CrossWire? It's not one

Re: [sword-devel] anniversaries

2017-01-10 Thread Greg Hellings
My HTTP server is not up right now, and that module was kept under password at all times to avoid it getting into the wrong hands. I still have all the files, but they're not publicly exposed. --Greg On Tue, Jan 10, 2017 at 11:16 AM, David Haslam wrote: > Greg Hellings

Re: [sword-devel] anniversaries

2017-01-10 Thread David Haslam
Greg Hellings own HTTP repo contains the NASB work in progress module. If any decisions are to be made, he should be involved. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/anniversaries-tp4656611p4656617.html Sent from the SWORD Dev mailing list archive at

Re: [sword-devel] anniversaries

2017-01-09 Thread Phil K
Sent: Monday, January 09, 2017 8:57 PM To: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] anniversaries On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote: I'm pretty sure the Lockman Foundation is not actually interested in releasing the NASB on Sword. You misunde

Re: [sword-devel] anniversaries

2017-01-09 Thread Kahunapule Michael Johnson
On 01/09/2017 03:56 PM, Karl Kleinpaste wrote: > On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote: >> I'm pretty sure the Lockman Foundation is not actually interested in >> releasing the NASB on Sword. > > You misunderstand. There has been a Lockman-sanctioned NASB in progress since >

Re: [sword-devel] anniversaries

2017-01-09 Thread Karl Kleinpaste
On 01/09/2017 08:47 PM, Kahunapule Michael Johnson wrote: > I'm pretty sure the Lockman Foundation is not actually interested in > releasing the NASB on Sword. You misunderstand. There has been a Lockman-sanctioned NASB in progress since 2004. ___

Re: [sword-devel] anniversaries

2017-01-09 Thread Kahunapule Michael Johnson
I'm pretty sure the Lockman Foundation is not actually interested in releasing the NASB on Sword. I could be wrong, but that is the impression I got when I last talked to them. On 01/09/2017 05:44 AM, Karl Kleinpaste wrote: > Today, NASB has been waiting 13 years. > NASB was last asked about

[sword-devel] anniversaries

2017-01-09 Thread Karl Kleinpaste
Today, NASB has been waiting 13 years. NASB was last asked about just this past weekend: [2017-01-08 01:34:20] <[nDy]> I am assuming that the NASB is not available on xiphos? It has been 2 years 13 days since last (1.7.4) Sword release. It has been 16 months 20 days since the abortive 1.7.5a1