Re: [sword-devel] NASB

2017-02-24 Thread Karl Kleinpaste
On 02/24/2017 04:48 PM, Kahunapule Michael Johnson wrote: > but who seem to grow weary or drop out when it comes to timely releases and > updates. ...as in, 2 years in need of a mere bugfix release. > I don't think we can expect to be taken as seriously as we would like to be. We are taken seriou

Re: [sword-devel] NASB

2017-02-24 Thread Kahunapule Michael Johnson
A slight correction: I have an NASB Sword module, but haven't done anything with it, because it had no place to go. I don't think Lockman is interested either in distributing it for free or selling it, right now. Honestly, the length of time that has been taken on the NASB module is embarrassin

Re: [sword-devel] NASB

2017-02-24 Thread Greg Hellings
On Fri, Feb 24, 2017 at 3:22 PM, TS wrote: > From what I can tell, a member named Kahunapule Michael Johnson seems to > be able to already create a NASB Sword module. > > This is according to his post here and from last year as well. > http://www.crosswire.org/pipermail/sword-devel/2017-January/0

Re: [sword-devel] NASB

2017-02-24 Thread TS
From what I can tell, a member named Kahunapule Michael Johnson seems to be able to already create a NASB Sword module. This is according to his post here and from last year as well. http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html I don’t quite understand why his posts k