Re: [sword-devel] NASB

2017-12-23 Thread Kahunapule Michael Johnson 
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 unlimited 
distribution of the Holy Bible in as many languages as possible. In English, we 
are blessed with multiple free options for truly unlimited free distribution of 
God's Word, so let's rejoice!

Thank you, TS, Greg, Troy, and all of you who contribute to this forum and the 
work of digital Bible distribution! I'm particularly happy about recent work on 
automating testing and release of new Sword software. Great job!

May God bless all of you, and grant you a Christmas filled with true peace and 
joy as only our Saviour can provide!
Michael

On 12/23/2017 12:12 PM, TS wrote:
> 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 refer to all his posts 
> in general which seems to be how my wording was taken. Also, I believe that 
> some time later an email was sent out (by the admin of the mailing list I 
> think?) letting everyone know that the mailing list server had some issues 
> during this period of time. So, perhaps this may be
> related as well to the confusion. At any rate though, I am sorry and do 
> apologize to Greg Hellings and, if needed, to Kahunapule Michael Johnson for 
> any offenses. None was meant. Greg's reply to what I had written regarding 
> Kahunapule's posts came across to me as a strong rebuttal and defense, but 
> also a misunderstanding. I think that I originally did not think that the 
> misunderstanding was worth replying to, but over time it has come to weigh on 
> me. Perhaps I'm being overly sensitive in this, but I do
> believe in honesty with others and trying to be "at peace with others" as 
> much as one can. So, it seemed good that I should write this.
>
> Sincerely,
> TS
>
> On Feb 24, 2017, at 01:47 PM, Greg Hellings  wrote:
>
>>
>>
>> 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/044041.html 
>> 
>>
>> I don’t quite understand why his posts keep getting ignored.
>>
>>
>> Kahunapule's posts are not ignored. Many of his are informative, rather than 
>> asking for response or help. But he is not ignored. For instance, he wasn't 
>> really looking for help in setting up his automated repository of modules - 
>> he was keeping the community apprised of his progress on it. And people have 
>> given him responses and feedback when appropriate.
>>  
>>
>>
>> He seems to have been in contact with the Lockman Foundation, but for 
>> some reason thinks or thought that the NASB Sword module would be for free.
>>
>> From what I understand from the forum discussions, in order for the NASB 
>> Sword module to be released, it would have to be a commercial module. Part 
>> of this means that it would obtainable through paying for it. So, the 
>> Lockman Foundation or Crosswire or some other entity would then host it on 
>> their website which allow for it to be downloaded only after paying for it. 
>> I’m guessing that a password would be provided to unlock the module.
>>
>>
>> It would not be sold by Crosswire. Crosswire is a non-income entity and does 
>> not sell any materials.
>>  
>>
>>
>> Can anyone tell me why Johnson's work is not being used? Generally 
>> speaking, could not Michael send it to Greg, Greg review it, and then if it 
>> passes, it be acceptable for release?
>>
>>
>> The goal was for us to be able to hand to Lockman, not a completed module, 
>> but a piece of software that they could feed their existing module through 
>> any time it changed and they could produce an updated version of the module 
>> themselves directly for distribution. So Kahunapule's work would not satisfy 
>> that requirement, unless he was starting from Lockman's internal text.
>>  
>>
>>
>> In addition to this, Greg himself already seems to have the work done in 
>> order to create the module. It seems that the real question is, does it work 
>> with all the major SWORD/JSword frontends? DM Smith confirmed last year that 
>> it worked with JSword and released a beta of BibleDesktop which supported it 
>> as well. The only two problems left (it possibly seems at least) based on DM 
>> Smith’s email

Re: [sword-devel] NASB

2017-12-23 Thread TS 

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 refer to all his posts in general which seems to be how my 
wording was taken. Also, I believe that some time later an email was sent out (by the 
admin of the mailing list I think?) letting everyone know that the mailing list server 
had some issues during this period of time. So, perhaps this may be related as well to 
the confusion. At any rate though, I am sorry and do apologize to Greg Hellings and, if 
needed, to Kahunapule Michael Johnson for any offenses. None was meant. Greg's reply to 
what I had written regarding Kahunapule's posts came across to me as a strong rebuttal 
and defense, but also a misunderstanding. I think that I originally did not think that 
the misunderstanding was worth replying to, but over time it has come to weigh on me. 
Perhaps I'm being overly sensitive in this, but I do believe in honesty with others and 
trying to be "at peace with others" as much as one can. So, it seemed good that 
I should write this.



Sincerely,

TS


On Feb 24, 2017, at 01:47 PM, Greg Hellings  wrote:






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/044041.html

I don’t quite understand why his posts keep getting ignored.



Kahunapule's posts are not ignored. Many of his are informative, rather than 
asking for response or help. But he is not ignored. For instance, he wasn't 
really looking for help in setting up his automated repository of modules - he 
was keeping the community apprised of his progress on it. And people have given 
him responses and feedback when appropriate.
 


He seems to have been in contact with the Lockman Foundation, but for some 
reason thinks or thought that the NASB Sword module would be for free.

From what I understand from the forum discussions, in order for the NASB Sword 
module to be released, it would have to be a commercial module. Part of this 
means that it would obtainable through paying for it. So, the Lockman 
Foundation or Crosswire or some other entity would then host it on their 
website which allow for it to be downloaded only after paying for it. I’m 
guessing that a password would be provided to unlock the module.



It would not be sold by Crosswire. Crosswire is a non-income entity and does 
not sell any materials.
 


Can anyone tell me why Johnson's work is not being used? Generally speaking, 
could not Michael send it to Greg, Greg review it, and then if it passes, it be 
acceptable for release?



The goal was for us to be able to hand to Lockman, not a completed module, but 
a piece of software that they could feed their existing module through any time 
it changed and they could produce an updated version of the module themselves 
directly for distribution. So Kahunapule's work would not satisfy that 
requirement, unless he was starting from Lockman's internal text.
 


In addition to this, Greg himself already seems to have the work done in order 
to create the module. It seems that the real question is, does it work with all 
the major SWORD/JSword frontends? DM Smith confirmed last year that it worked 
with JSword and released a beta of BibleDesktop which supported it as well. The 
only two problems left (it possibly seems at least) based on DM Smith’s email 
are:

1) Does the Sword engine support having the lex as a single module (which is 
apparently a requirement from the Lockman foundation)? This would mean, for 
example, that Strong’s would have “G” (Greek) and “H” (Hebrew”) both as “keys”. 
(I’m guessing having more than one key is the problem or the order of the keys 
is? Would having them in the same module be a problem? Would having two 
different keys be a problem or would the order of “G” and then “H” be a 
problem?)



I don't know if the engine supports this. It's a worthy question.



2) Does the text display the same on BibleDesktop, SwordWeb and The SWORD 
Project for Windows? Apparently there’s a word which is accented differently?



There is a third item, and that is one of the bigger problems - there is more 
than just the NASB in the module set originally provided by Lockman. Troy 
requires that all of the modules build equally well off of the same codebase in 
an automated fashion. I ran into an issue with one of the modules that 
introduces a character set not present in the NASB. One of the characters in 
the set is represented the same way as a portion of the NASB markup but with 
very different semantics. I had, at the time,

[sword-devel] Announcing release 1.8.0

2017-12-23 Thread Greg Hellings 
I would like to take this chance to announce the immediate availability of
SWORD release 1.8.0.

I know this release has been a long time in coming, but the long time comes
with lots of benefits for users, developers, and maintainers. The benefits
to users and developers are mentioned elsewhere, throughout the code and
other places. The main benefit to maintainers is that, now, there are
automated tests in place and the release process is now automated. This
means that future releases on that 1.8 branch can be easily executed
whenever needed.

Have a Merry Christmas, everyone! And keep your eyes open for a 1.8.1 in
the not too distant future to fix up buildings in the binding code.
Otherwise, you can get the code you're looking for below:

MD5: 095dbd723738c2a232c85685a11827a8 sword-1.8.0.tar.gz

SHA512:
c45f3135255322a77e955297997db2529f31b397c42cc4b9474dc6ec8d329b2233b292078979de5fbf33cad4a1a607aabb66f86501072a729d68e9fc840c8c8e
 sword-1.8.0.tar.gz

URL: http://crosswire.org/ftpmirror/pub/sword/source/v1.8/sword-1.8.0.tar.gz

--Greg
___
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

Re: [sword-devel] Introducing myself, SwordHammer, and asking a ton of questions

2017-12-23 Thread jhphx 

On 12/23/2017 7:28 AM, Tom Sullivan wrote:
 A rather famous case is where a mobile home (house on wheels) was 
called "Holiday Rambler." American Motors (now defunct) sued because 
they had a car called "Rambler." They lost because the products were 
so unlike one another.


It may be worth noting, or not, that they did get sued. Sometimes 
lawyers will advise to sue to establish a precedent of defending their 
trade mark. Undefended trade marks become harder to defend and risk 
becoming public domain.


Just my non-professional understanding and I could be wrong.

It may be worth considering how willing you would be to defend the name 
if sued. Personally I think you should be fine but what do I know.


Jerry


___
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

Re: [sword-devel] Introducing myself, SwordHammer, and asking a ton of questions

2017-12-23 Thread Tom Sullivan 

David:

Thank you. I never thought of that. However, trying SwordHammer in 
Startpage, Google, and Bing only bring up a bunch of weird stuff, and 
only one hit where "SwordHammer" is one word, not two. That hit is a 
fantasy magazine of some sort. USA trademark law says that in order for 
there to be infringement, the products marked must be similar enough to 
cause confusion. A rather famous case is where a mobile home (house on 
wheels) was called "Holiday Rambler." American Motors (now defunct) sued 
because they had a car called "Rambler." They lost because the products 
were so unlike one another.


But thanks. Good thing to check.

Tom

Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God created you, owns you and gave you commands to obey.
You have disobeyed God - as your conscience very well attests to you.
God's holiness and justice compel Him to punish you in Hell.
Jesus Christ became Man, was crucified, buried and rose from the dead
as a substitute for all who trust in Him, redeeming them from Hell.
If you repent (turn from your sin) and believe (trust) in Jesus Christ,
you will go to Heaven. Otherwise you will go to Hell.
Warning! Good works are a result, not cause, of saving trust.
More info is at www.esig.beforgiven.info
Do you believe this? Copy this signature into your email program
and use the Internet to spread the Great News every time you email.

On 12/23/2017 09:04 AM, David Haslam wrote:

A Google search for SwordHammer gives lots of higher profile hits.

Wondering if Tom's project name is at risk of infringing a registered 
trademark.


Worthwhile exercising due diligence at this early stage.

Not too late to rebrand it if there turns out to be a conflict.

David

Sent from ProtonMail Mobile




__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__


___
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

Re: [sword-devel] sword-devel Mailing list server issue

2017-12-23 Thread David Haslam 
The extract from the email header mentions protonmail.com

I recently started using ProtonMail to communicate with this mailing list.
I had been using a different address and method for the last eight years, but 
that stopped working inexplicably on 26 November.

I could well be the only one using a ProtonMail address here.
Messages that I send to the list are also displayed with a warning when the 
same message comes back to me from the CrossWire server.

I have already asked our admin what's wrong and could there be something 
configured in correctly in our mail server.

Best regards,

David

>___
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

Re: [sword-devel] Introducing myself, SwordHammer, and asking a ton of questions

2017-12-23 Thread David Haslam 
A Google search for SwordHammer gives lots of higher profile hits.

Wondering if Tom's project name is at risk of infringing a registered trademark.

Worthwhile exercising due diligence at this early stage.

Not too late to rebrand it if there turns out to be a conflict.

David

Sent from ProtonMail Mobile

>>
>
> @beforgiven.info>___
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