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. Many of my sources will be simple webpages, such as http://www.aina.org/books/bftc/bftc.htm I apologize if I opened an old wound of sorts. Or if the case is not relational, but rather their theology of some kind, I understand. Just know, I have no awareness of any sort of situation relating to the matter. Just that it's a Bible study software engine/format. On Tue, Feb 21, 2017 at 3:06 PM, Greg Hellings <greg.helli...@gmail.com> wrote: On Tue, Feb 21, 2017 at 3:59 PM, Matt Zabojnik <matt...@gmail.com> 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 text is under Copyright by Lockman. Distributing the work would not be legally permitted without obtaining their permission. Thank you. I have permission. You have permission to distribute an NASB module from Lockman? That's interesting. It's important for our own resources to know whence the upstream work was found. I see. That being the case, there's no reason I wouldn't be able to convert a PD work from Zefania XML for example, or any other format I find it in, correct? >From a technical perspective, you can convert from any source you can find into a module for your own use. And from a technical perspective, it's very easy to host your own module repository - requiring nothing more than an accessible HTTP serving software. As for Zefania, I don't believe you'll get much support or encouragement from these parts surrounding Zefania. --Greg Thank you for your ongoing support and information. It is indeed very helpful. Blessings, Matt On Tue, Feb 21, 2017 at 1:50 PM, Greg Hellings <greg.helli...@gmail.com> wrote: On Tue, Feb 21, 2017 at 2:45 PM, Matt Zabojnik <matt...@gmail.com> 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. Those who need to know them, already know them. I haven't yet started working on this module, but the intent will be mass distribution rather than personal use only. The text is under Copyright by Lockman. Distributing the work would not be legally permitted without obtaining their permission. Is it common for people to convert stuff for personal use? And how important is it to declare where I obtained a source text for public domain materials? I didn't see coverage on either of those in the wiki. It's important for our own resources to know whence the upstream work was found. This allows repeatable module generation should the upstream source ever be updated and corrected. Very often problems are uncovered in upstream works during the module creation process and this typically continues once the module is in users' hands. The NASB, however, is not a public domain work. --Greg On Tue, Feb 21, 2017, 12:15 PM Greg Hellings <greg.helli...@gmail.com> wrote: 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 various reasons, abandoned the work. Most recently it was me, and I gave up due to a lack of a consistent or realistic objective for delivery of the results to Lockman. You can, essentially, assume that nothing more will ever come of it from the official channel. You'd be best to pursue converting another digital source for your own personal use. --Greg On Tue, Feb 21, 2017 at 1:06 PM, Matt Zabojnik <matt...@gmail.com> wrote: 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-man on tyre work that's already been done there? _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 -- ------------------------------------------ PGP ID: 0x5fa5cbaecfd5690c ------------------------------------------ _______________________________________________ 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 _______________________________________________ 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 -- ------------------------------------------ PGP ID: 0x5fa5cbaecfd5690c ------------------------------------------
_______________________________________________ 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