[sword-devel] NASB status

Peter Von Kaehne refdoc at gmx.net
Wed Jan 6 08:22:07 MST 2016


That makes little sense. Many a time only attractive modules available have changed the glacial speed by which some frontends improve. I much rather would deal on the support line with complaints about NASB not working well on whatever than it still not available.

Peter


> Von: "Greg Hellings" <greg.hellings at gmail.com>

> The software requirement was JSword support - I forget which feature
> it was that was needed, but Troy didn't want to proceed until
> JSword/BibleDestktop fully supported the features.
> 
> --Greg
> 
> On Wed, Jan 6, 2016 at 8:53 AM, Karl Kleinpaste <karl at kleinpaste.org> wrote:
> > NASB has been a decade-plus in progress.
> >
> > Last I knew or remembered, Greg's markup had gotten quite solid and, I
> > believe, finalized.  There was something going on about necessary engine
> > support percolating out to one or more of the frontends before NASB would be
> > considered for release.  Where do we stand on that?
> >
> > Seriously, 12 years. How much longer?
> >
> > _______________________________________________
> > sword-devel mailing list: sword-devel at crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 



More information about the sword-devel mailing list