Thanks for the feedback, Fr. Cyrille. I'll have a look at the remaining ticket
and pass it on to Lockman if it's appropriate. I appreciated you checking all
the other tickets against the NASB.
On September 17, 2022 10:55:43 PM GMT+02:00, Fr Cyrille
wrote:
>Hi Troy,
>Thank you very much for thi
Hi Troy,
Thank you very much for this update. I checked all the issues on the
tracker only one is still present (and maybe the lockman foundation is
interesting to know it?):https://tracker.crosswire.org/browse/MOD-393
Le 17/09/2022 à 14:27, Troy A. Griffitts a écrit :
Dear Team,
Lockman has
Dear Team,
Lockman has given us updated data for their NASB 1995 module (our
current module) and their new NASB 2020 edition.
I have updated our conversion script to convert their latest data
https://crosswire.org/svn/sword-tools/trunk/modules/nasb2020/
and have posted the two new modules on
Troy wrote,
"No. diatheke is certainly not the gold standard for seeing anything.
Diatheke has bugs of its own.
I personally use word/examples/cmdline/lookup.cpp to check all info
about what SWORD output from a module entry to a frontend for a particular
format.
Diatheke
This is also a challenge for using USFM, let alone OSIS and SWORD front-ends.
In some AV11N, the CT is sometimes only part of verse 1.
There are also at least 2 Psalms where the CT extends into verse 2 and 1 Psalm
where the CT actually creeps into verse 3 with a single word consisting of a
ver
Hi Tom,
It's very easy to create a deb with the xiphos sources. Just see the
"Generating DEB Packages" in the install.md. Then you'll have the last
release.
Le 08/05/2020 à 19:59, Tom Sullivan a écrit :
> Y'all:
>
> Thank you all for your interactions. I honestly have been trying to
> help, not ju
While the OSIS spec has one definition of canonical, being part of the
published text. Regarding Bibles, Troy pointed out, we use it in the
theological sense for Bible modules.
There are many versifications that have the canonical titles as verse 1. and
what we have as verse 1 to n in verse 2 t
Hi Tom,
Thank you. I do realize you are not trying to waste anyone's time and
your frustrations with our lack of supply clear version strings are
noted. Great suggestion for improvement, thank you.
To improve this, I have just committed new logic to add the "repository
revision" into the the na
Aside: Where do all the fancy colours come from, that I don’t see in Xiphos on
Windows ?
NB. Except in the Preview pane for some types of search results when the search
key (or part if it) is yellow highlighted.
David
Sent from ProtonMail Mobile
On Fri, May 8, 2020 at 14:28, Karl Kleinpaste
The original Hebrew text had no “verse numbers”.
It’s anachronistic to assert that it did.
See
[https://en.wikipedia.org/wiki/Chapters_and_verses_of_the_Bible](https://en.wikipedia.org/wiki/Chapters_and_verses_of_the_Bible?wprov=sfti1)
Modern printed editions of the MT have verse numbers “retro
Closed. Mea culpa.
Thanks to DM for explaining.
“The pre-verse div is a construct by osis2mod. These are milestoned to mark the
beginning and end of pre-verse material.”
Sent from ProtonMail Mobile
On Fri, May 8, 2020 at 14:22, David Haslam wrote:
> I have created issue MOD-367 for this modu
I think our replies crossed in the ether, Tom.
Canonical is simply not a theological matter in OSIS.
David
Sent from ProtonMail Mobile
On Fri, May 8, 2020 at 15:28, Tom Sullivan wrote:
> Y'all:
>
> Thanks David.
>
> The Psalm titles are considered canonical because they are the Word of
> God!
One of the subtleties of OSIS is that the canonical attribute is actually not a
theological matter.
It’s easy to jump to the wrong conclusion that SWORD treats it as if it was.
It’s actually a technical attribute relating to the published work it
represents in digital format.
So it can just as
The difference is that JSword never hides titles with canonical=“true” even
with Headings OFF.
SWORD does and always has done.
David
Sent from ProtonMail Mobile
On Fri, May 8, 2020 at 15:00, Tom Sullivan wrote:
> Karl:
>
> I cannot explain the difference between your linked picture and my
> r
Y'all:
Thank you all for your interactions. I honestly have been trying to
help, not just waste everybody's time. But I am not a C++ programmer. I
know enough Python to be dangerous. I can do some occasional maintenance
on C. All the languages I once knew are obsolete or specific to
Microsoft
Two locations in the NASB module are incorrectly versified.
The text for 2 Chron 6.41 appears in & with verse 42.
The text for Isaiah 37:15 appears in & with verse 16.
My printed copy is the 1972 First Edition of the complete NASB.
AFAIK, there would have been no strong reason for Lockman to ha
I have created issue MOD-367 for this module bug.
David
Sent from ProtonMail Mobile
On Fri, May 8, 2020 at 13:55, David Haslam wrote:
> Is this simply because the OSIS file used for module build made use of the
> milestone form of the div element ?
>
> SWORD does not support that, IIRC.
>
> I
So, a few things here.
On 5/8/20 9:57 AM, Tom Sullivan wrote:
> Troy, Karl:
>
> (Karl:
> [NASB]
> Heading=On)
I have no idea what you are showing here. This looks like a .conf
setting. Xiphos may pay attention to Heading=On, but this doesn't mean
anything to SWORD.
> I am using Debian Buster
Troy, Karl:
(Karl:
[NASB]
Heading=On)
I am using Debian Buster (10) (stable). This is the current stable
version of Debian and is the one generally recommended. It is the
version those of us who have work to do use, rather than mess with a
buggy OS. (There is a more recent Debian version gene
Is this simply because the OSIS file used for module build made use of the
milestone form of the div element ?
SWORD does not support that, IIRC.
I just looked at the mod2imp dump for the NASB.
There are 2250 instances of this type of div, each with an sID and an eID.
Aside: Repeating the type
On 5/8/20 12:30 PM, Troy A. Griffitts wrote:
> It sounds like Karl is saying that the latest version of
> Xiphos works. Is this correct?
Tom's report seems to indicate that no headers are displayed, no matter
what he does. This makes no sense to me, because headers on/off has been
part of Xiphos
Good morning!
So, lots of conversation. I've read it all and can't determine if there
is still a problem to be fixed.
First, it sounds like Tom is using an old version of software. Please
be sure you are using the latest version of software before pursuing
problems. It sounds like Karl is sayi
My reference to verse numbers was only to show that others also
considered the Psalm titles to be canonical.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
On 5/8/20 11:01 AM, David Haslam wrote:
The original Hebrew text had no “verse numbers”.
It’s anachronistic t
On 5/8/20 10:49 AM, Tom Sullivan wrote:
> My Biblia Hebraica treats Psalm titles as the first verse, indicating
> biblical canonacity and in line with Hebrew versification.
No one is questioning canonicity.
It's a matter of some code, and whether it fully represents what was
intended. In other
The pre-verse div is a construct by osis2mod. These are milestoned to mark the
beginning and end of pre-verse material.
DM
> On May 8, 2020, at 8:55 AM, David Haslam wrote:
>
> Is this simply because the OSIS file used for module build made use of the
> milestone form of the div element ?
>
Y'all:
My Biblia Hebraica treats Psalm titles as the first verse, indicating
biblical canonacity and in line with Hebrew versification.
Note the following from OSIS doc, OSIS.pdf:
Appendix B.2.10 titles
The type attribute on the title element is used to allow special
rendering of particular
osis2mod preserves properly marked Psalm titles before verse 1 as part of that
verse. Other titles (and other pre-verse content) will either be put in verse 0
or in verse 1 based on other considerations. This is documented in the wiki for
osis2mod.
In Him,
DM
> On May 8, 2020, at 10:28
Y'all:
Thanks David.
The Psalm titles are considered canonical because they are the Word of
God! If Sword does not display them when the user would expect them,
that that is monkeying with God's Word and completely unacceptable. The
Psalm titles are theologically and exegetically significant.
On 5/8/20 10:00 AM, Tom Sullivan wrote:
> because Psalm titles are canonical, front-ends should put a difference
> in display between them and human editor supplied titles.
It's a fine idea, but it requires (in the xhtml case) the engine to wrap
such titles in a suitable so that a CSS control can
Karl:
I cannot explain the difference between your linked picture and my
results on Xiphos 4.1.0. The problem survived unchecking/rechecking and
reboot.
But if you look at my first email, you will note that diatheke does
produce Psalm titles for ESV2011 and KJV, but after the first verse. Yo
On 5/8/20 8:21 AM, Tom Sullivan wrote:
> Yes, the box is checked.
The reason I ask is that I see this just fine in Xiphos.
http://karl.kleinpaste.org/xiphos/nasb-ps-5-1.png
(pardon the colors, I do CSS things to make certain stuff really obvious.)
diatheke doesn't produce headers, not even when
Yes, the box is checked.
Note also that diatheke has the same problem.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
On 5/8/20 7:06 AM, Karl Kleinpaste wrote:
On 5/8/20 5:55 AM, Tom Sullivan wrote:
Xiphos 4.1.0 displays titles for ESV2011, not NASB
Have you enabl
On 5/8/20 5:55 AM, Tom Sullivan wrote:
> Xiphos 4.1.0 displays titles for ESV2011, not NASB
Have you enabled headings in NASB's module options?
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Y'all:
The NASB module, in combination with Sword, does not seem to treat Psalm
titles as canonical. As noted below, JSword does not seem to have the
problem, Sword does. So is there some incompatibility or bad OSIS going
on here?
Thanks.
Details below. Comparisons with other modules.
$ os
Ah, I have tried the latest release (there hasn't been an update since
first public availability, but there have been a number of revisions in
testing for a while now) on Bishop on Android and it generally shows
these verses correctly with footnotes on and in "Language Assist" mode,
which highligh
On Thu, 2020-04-02 at 20:54 +, David Haslam wrote:
> Both Bible modules work correctly in PocketSword in regard to the
> display of Strong’s lookup with an installed dictionary module.
>
> NB. I have StrongsRealGreek and StringsRealHebrew modules installed
> from the Xiphos repository.
>
> Ma
I have submitted a PR that removes the NASHebrew/NASGreek handling code in
Xiphos. With it applied, clicking on Strong's numbers now works as expected.
Fedora packages with the applied patch are building now and will be ready
shortly. Any other packagers wishing to include this fix ASAP can fetch
Thanks Karl. All working as it should.
Regards, Gary
On Thu, 2020-04-02 at 17:49 -0400, Karl Kleinpaste wrote:
> On 4/2/20 4:40 PM, G&J Bennett wrote:
> > I generally use two modules that contain Strong's numbers - the
> > ESV2011
> > and NASB. The ESV2011 works correctly, but the NASB doesn't.
>
On 4/2/20 4:40 PM, G&J Bennett wrote:
I generally use two modules that contain Strong's numbers - the ESV2011
and NASB. The ESV2011 works correctly, but the NASB doesn't.
Oh...well, um...crap.
/sigh
/Bother, said Pooh.
See, once upon a midnight dreary, lo these ages ago, in the Before
Times,
Both Bible modules work correctly in PocketSword in regard to the display of
Strong’s lookup with an installed dictionary module.
NB. I have StrongsRealGreek and StringsRealHebrew modules installed from the
Xiphos repository.
Maybe there’s an issue for the StrongsGreek and/or StrongsHebrew modu
Hello,
I'm using Xiphos on Void Linux under Flatpak and have an issue with the
recently-released unlocked NASB module. I don't know if the issue is a
user, Xiphos or a module issue so need some guidance please.
I generally use two modules that contain Strong's numbers - the ESV2011
and NASB. The
Hello,
I'm using Xiphos on Void Linux under Flatpak and have an issue with the
recently-released unlocked NASB module. I don't know if the issue is a
user, Xiphos or a module issue so need some guidance please.
I generally use two modules that contain Strong's numbers - the ESV2011
and NASB. The
The F-Droid version takes a bit longer to update than the one in the play
store, so if you have that version, you'll have to wait.
Or you can zip the module files up from the .sword directory on your
computer and import them AndBible.
___
sword-devel mai
Le 14/03/2020 à 10:24, David Haslam a écrit :
> Update And Bible as advised earlier.
Andbible seems to be update: 3.2.340. And I can read the notification of
the release with the support of the Lockman fondation.
>
> Install the latest version from the Play Store.
>
> David
>
> Sent from ProtonM
Update And Bible as advised earlier.
Install the latest version from the Play Store.
David
Sent from ProtonMail Mobile
On Sat, Mar 14, 2020 at 09:20, Cyrille wrote:
> Hello,
> Me too, I can't find Nasb in the Andbible module manager. Any idea?
>
> Le 13/03/2020 à 20:01, John Dudeck a écrit :
Hello,
Me too, I can't find Nasb in the Andbible module manager. Any idea?
Le 13/03/2020 à 20:01, John Dudeck a écrit :
> Aha! I looked at my phone and there was a pending update for AndBible.
> Ran the update and now NASB is there.
>
> Still waiting for configurable repositories...
>
> John
>
> -
These are great news, Troy! I've been a happy NASB reader when studying
the Bible in English!
Thanks for your efforts on this long road and thanks to Lockman! I
remember writing them an email ten years ago asking about the copyright
of the NASB. To see now that this translation becomes availab
Aha! I looked at my phone and there was a pending update for AndBible. Ran the update and now NASB is there.
Still waiting for configurable repositories...
John
David Haslam wrote:
See the And Bible Facebook page.
NASB is now available for free in And Bible due to Crosswire's new di
See the And Bible Facebook page.
NASB is now available for free in And Bible due to Crosswire's new distribution
contract! To use NASB (or LBLA or NBLA), please update to the latest version of
And Bible first; update is now available in Play Store (3.2.343).
Sent from ProtonMail Mobile
On Fri,
From the announcement on their Facebook page.
NASB is now available for free in And Bible due to Crosswire's new distribution
contract! To use NASB (or LBLA or NBLA), please update to the latest version of
And Bible first; update is now available in Play Store (3.2.343).
Regards,
David
Sent f
There is currently no way to add repositories in AndBible. I looked at the App code, and realized that it's not just a matter of
hacking a URL string. It is also dependent on JSword, and there is repository-specific code for the three repositories that are
available.
There are requests for th
Great news that the NASB modulevis available! Probably not the place for
this question, but it is in response to this news, so I'll ask anyway. I
wanted to use the module on AndBible, but it doesn't look like there is a
way to add the Lockman foundation's repository as a source. Has anyone done
thi
Regarding the NASB 2020 text, here is the word from Lockman:
We're not releasing the NASB 2020 in software until the print editions are
available toward the end of this year. I don't have a date yet. Then we'll look
at free software sometime in 2021 after the commercial release.
On March 13, 20
There's also a NASB2020 in limited preview release right now.
NASB will remain 1995 edition? Does the license stipulate whether updates
are mandatory?
On Fri, Mar 13, 2020 at 7:48 AM Tom Sullivan wrote:
> Y'all:
>
> There was a request to change the module NASB to NASB95. Is this in the
> wor
Y'all:
There was a request to change the module NASB to NASB95. Is this in the
works or will it remain NASB? There are in fact, two versions of the
NASB out there as those who have the older (especially print) version know.
Thanks.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
---
Refresh sources and re-install it.
The released NASB module is not locked.
Read the earlier message from Troy with the official announcement.
David
Sent from ProtonMail Mobile
On Fri, Mar 13, 2020 at 08:14, John A. Sullivan III
wrote:
> Hello, all. I was absolutely thrilled to see the Lockm
Hello, all. I was absolutely thrilled to see the Lockman Foundation
now appear in the Bibletime bookshelf options and I downloaded the NASB
module. I was about to purchase a key from Lockman but I see notes on-l
ine that the module cannot yet be unlocked and is only for testing. I
don't know if t
This is great news, Troy! Praise God!
On 3/11/20 6:42 PM, Troy A. Griffitts wrote:
> It's been a long long road, but after much negotiation and many
> volunteers contributing to the conversion efforts, we have finally been
> granted permission to distribute Lockman's:
>
> New American Standard Bib
No - PocketSword's module unlock dialog only appears for a locked module as
soon as you select it after installing it. It would only reappear if you had
clicked either No or Cancel rather than Yes and entered a correct key. I just
tried using the NA28 to confirm this behaviour.
An unlocked modu
Michael,
Yep - that's a good suggestion, and worth a try.
Use Module Maintainer Mode in PocketSword to xfer it from my PC.
One has to first Archive the renamed module to a Zip file, but that's readily
done using Xiphos MM.
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Sec
Bishop had the same issue moving from a locked module to a module without
enciphering.
Bishop lets you change your unlock key in the About section where it shows each
module's About information. Is there a place in PocketSword which lets you
update your unlock key? Maybe where you can see the Ab
David,
Could you pull the work, rename the conf file and offline install it as
NASB1995?
On Thu, Mar 12, 2020 at 3:25 AM David Haslam wrote:
> Anyone got any good suggestions that don’t involve deleting the
> PocketSword app?
>
> Rebooting the iPad Mini didn’t help.
>
> David
>
> Sent from Prot
With the official announcement from Troy, I have taken the liberty to add a
subsection in our Wiki page.
https://wiki.crosswire.org/Official_and_Affiliated_Module_Repositories#Lockman_Foundation
Understand that this repository is on our server, unlike the Affiliated
repositories shown further d
Le 12/03/2020 à 13:47, Karl Kleinpaste a écrit :
> On 3/12/20 8:01 AM, Fred Smith wrote:
>> Now, in my ignorance I find I don't know how to set up the "Lockman
>> Foundation" repository in Xiphos.
> Open module manager.
> Click Add/Remove in left panel.
> Click Load Standard at bottom.
>
I opened
Got it, thank you.
Johan
-Original Message-
From: Fred Smith
Sent: Thursday, 12 March 2020 14:47
To: sword-devel@crosswire.org
Subject: Re: [sword-devel] NASB, NBLA, LBLA
On Thu, Mar 12, 2020 at 12:10:12PM +, David Haslam wrote:
>You can refresh sources in the Xiphos mod
On 3/12/20 8:01 AM, Fred Smith wrote:
Now, in my ignorance I find I don't know how to set up the "Lockman
Foundation" repository in Xiphos.
Open module manager.
Click Add/Remove in left panel.
Click Load Standard at bottom.
___
sword-devel mailing li
On Thu, Mar 12, 2020 at 12:10:12PM +, David Haslam wrote:
>You can refresh sources in the Xiphos module manager.
Thanks David, Cyrille! I'm all set now.
Johan, see either David's instructions below, or the reply from Cyrille
to find out how to do this.
Thanks to all, again!
Fred
>
>
I am with you Fred, I don’t know where / how to find the "Lockman Foundation"
repository in Xiphos.
Johan Marais
> On 12 Mar 2020, at 14:02, Fred Smith wrote:
>
On Wed, Mar 11, 2020 at 09:42:53PM -0700, Troy A. Griffitts wrote:
> It's been a long long road, but after much negotiation and many
You can refresh sources in the Xiphos module manager.
Click the Load Standard button
It should then appear as one of the repositories from our updated Master
Repositories List.
Advanced users might wish to first save a copy of the previous InstallMgr.conf
file
David
Sent from ProtonMail Mobi
Le 12/03/2020 à 13:01, Fred Smith a écrit :
> On Wed, Mar 11, 2020 at 09:42:53PM -0700, Troy A. Griffitts wrote:
>> It's been a long long road, but after much negotiation and many
>> volunteers contributing to the conversion efforts, we have finally been
>> granted permission to distribute Lockma
On Wed, Mar 11, 2020 at 09:42:53PM -0700, Troy A. Griffitts wrote:
> It's been a long long road, but after much negotiation and many
> volunteers contributing to the conversion efforts, we have finally been
> granted permission to distribute Lockman's:
>
> New American Standard Bible (NASB)
> Nuev
On Thu, Mar 12, 2020 at 7:45 AM Troy A. Griffitts
wrote:
> It's been a long long road, but after much negotiation and many
> volunteers contributing to the conversion efforts, we have finally been
> granted permission to distribute Lockman's:
>
> New American Standard Bible (NASB)
> Nueva Biblia
Anyone got any good suggestions that don’t involve deleting the PocketSword app?
Rebooting the iPad Mini didn’t help.
David
Sent from ProtonMail Mobile
On Thu, Mar 12, 2020 at 07:34, David Haslam wrote:
> Actually, none of the 3 reinstalled modules work for me because PocketSword
> had remem
Thanks to all for this!
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
On 3/12/20 12:42 AM, Troy A. Griffitts wrote:
It's been a long long road, but after much negotiation and many
volunteers contributing to the conversion efforts, we have finally been
granted permission to distribute Lock
Actually, none of the 3 reinstalled modules work for me because PocketSword had
remembered yesterday’s unlock keys.
There’s probably no way to clear them out short of deleting the app.
It’s not as if anyone can manually tweak some hidden file where these keys were
saved.
IPadOS just isn’t like
Thanks Troy.
Just deleted all 3 and re-installed them successfully in PocketSword on my iPad
Mini 4.
Please could you look towards creating the downloadable search indices for
PocketSword to find on our server.
Best regards,
David
Sent from ProtonMail Mobile
On Thu, Mar 12, 2020 at 04:42, T
It's been a long long road, but after much negotiation and many
volunteers contributing to the conversion efforts, we have finally been
granted permission to distribute Lockman's:
New American Standard Bible (NASB)
Nueva Biblia de las Américas (NBLA)
La Biblia de las Américas (LBLA)
Additionally,
Thank you, TS. No offense was taken, here. For now, my NASB module can just
rest in its copyright prison, as does Greg's. I'm sure both are great from a
technical standpoint. The Lockman Foundation seems open to some limited
distribution of the NASB, but for now, I am much more interested in unl
Hi, I know that this post is old, but I believe that I need to clarify
something(s).
At the very beginning of my earlier email (below with Greg's replies), when I was
writing about Kahunapule's posts, I just meant his posts about the NASB in specific being
ignored. I was not meaning to
Just so you're not unaware that there are related discussions outside this
thread.
As from three days ago, David I-B was going to email Troy about the NASB
module that STEP Bible has, but for which they don't have permission to make
available outside of STEP Bible.
As there's a decade or more of
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
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
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
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
On Wed, 2017-02-22 at 22:55 +, Matt Zabojnik wrote:
> . Could you point me to a
> reliable resource that I can use to find out who the copyright owners
> are for public domain resource, in order to request permission to
> distribute? I'm not asking you to do the leg work for me, but perhaps
> t
Yes sir, I forgive you, and can see how easily this could have been
misunderstood. I didn't intend on the dual conversation all in one thread,
I didn't expect the public domain question to be as extensive as it became.
I've not made any indication that I might freely distribute the NASB, nor
am I u
Matt,
A couple things. I think What Jonathon and others on here are saying
is, that over 30 years doing this stuff, we've learned that the ONLY
source that is reliable to both: obtain the data for a Bible, and to
obtain permission to host a Bible, is the actual owner / copyright holder.
We
I apologize for the confusion here, this really should have been two
threads, as two conversations are occurring simultaneously.
I have permission in regards to NASB.
On the other hand, what started as a simple question about declaring PD
sources ended up commanding the direction of the thread.
I
On 02/21/2017 11:37 PM, Matt Zabojnik wrote:
> know, I have no awareness of any sort of situation relating to the matter.
Let's put it this way: Other than official resources distributed by
authorized agents of _The Sword Project_, _Accordance_, _BibleWorks_,
and _Logos Library Systems_ (I've for
Thank you, David.
I'm going to take up the NASB work. I won't need anyone's work that has
already been done on this, though if anyone would like to give input, I
don't mind.
I appreciate the depth of your explanation for source texts and for all of
the clarification you've provided.
The only sou
The internet is rife with plagiarised works that are posted online without
any provenance!
It's important to CrossWire that each of our modules has a provenance for
its source text which must be one that is hosted by a reputable agency with
a clearly demonstrated direct interest in the work.
An u
Thanks for the info, I'm going to labor to convert stuff, and I'm using S3
as my repository for now.
I'm completely unaware of any politics surrounding Crosswire/SWORD and any
other module format, I just chose Zefania as an example, though I could
have mentioned e-sword, kindle, nook, pdf, etc. Ma
On Tue, Feb 21, 2017 at 3:59 PM, Matt Zabojnik wrote:
> The reasons are deep and political. Those who need to know them, already
>> know them.
>
> I appreciate your discretion in your answer. Conversion difficulties was
> what I was primarily concerned with, so this is, in a sense, good news.
>
>
> The reasons are deep and political. Those who need to know them, already
> know them.
I appreciate your discretion in your answer. Conversion difficulties was
what I was primarily concerned with, so this is, in a sense, good news.
The text is under Copyright by Lockman. Distributing the work
On Tue, Feb 21, 2017 at 2:45 PM, Matt Zabojnik wrote:
> Thanks for the info!
>
> Would you mind explaining in different terms your reason for aborting the
> project? I didn't fully understand. Delivering to Lockman wasn't going to
> work for some reason?
>
The reasons are deep and political. Thos
Thanks for the info!
Would you mind explaining in different terms your reason for aborting the
project? I didn't fully understand. Delivering to Lockman wasn't going to
work for some reason?
I haven't yet started working on this module, but the intent will be mass
distribution rather than persona
The Tyndale STEP (the JSword based app) team will be releasing a Tyndale
House edition of the NASB as a SWORD module.
Dr David Instone-Brewer has let me have a prerelease copy of the module.
Here's a line from the .conf file.
About=The Holy Bible, New American Standard Version. Copyright © 1995
Eons ago, Crosswire received permission from Lockman to begin work on an
NSAB module that they could commercially deliver to users who paid for it.
Many people have tackled the work of performing the conversions from
Lockman's internal, proprietary markup to a Sword module. Each one has, for
vario
What's the status on the NASB module? I saw it mentioned in the dictionary
message. This is the first I've heard of it, being new to sword devel.
I'm currently working to convert NASB with strongs, footnotes and
references, but I need to learn OSIS and RegEx better first.
Who here is the point-ma
Greg's
Version=0.1.7
SwordVersionDate=2014-04-02
That's the latest version in his private repository.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/NASB-status-tp4655601p4655658.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
_
1 - 100 of 169 matches
Mail list logo