[sword-devel] Correction for KJV module in 2 Corinthians 1:8
Fr Cyrille
fr.cyrille at tiberiade.be
Sun Jan 22 04:22:44 EST 2023
Le 16/01/2023 à 22:34, Troy A. Griffitts a écrit :
> Hey guys. A few points of clarity.
>
> We do make the source available from our wiki page regarding the work.
>
> https://wiki.crosswire.org/User:Dmsmith/KJV_2.6
>
> You will find a link to the source somewhere on that page.
>
> DM Smith took over that work after we finished the KJV2003 work to
> manually add the Strongs numbers to the NT. He still holds that
> pumpkin. It seems he has been away for quite some time though, so
> maybe we can discuss if anyone feels called to take over that work and
> we can ask DM how he feels about that.
>
> I would like to keep our official version, which is the source for
> almost every KJV digital text out in the wild with Strongs numbers,
> under our control for quality assurance, so at git.crosswire.org, but
> certainly we've never had the intention to conceal the source. We want
> people to use it. That's why we made it!
>
> Troy
Hi,
Thinking about the copyright issue, I don't think it's necessary to put
the kjv on the private part of our git (git.crosswire.org). The normal
gitlab is quite enough if we only want to control the proposed changes.
We know well that on git every merge request must be approved. Moreover,
the whole process of updating modules is entrusted to the module team.
So I propose to go for the simplest solution which is to put the kjv
text on the open gitlab.
Troy do you intend to move in this direction?
Or will this case drag on for years?
Best regards, br Cyrille
>
> On January 16, 2023 1:24:17 PM PST, Robert Hunt
> <hunt.robertj at gmail.com> wrote:
>
> Thanks Michael for that (although I haven't heard of the Beaver
> Scriptures and my search engines gave no help).
>
> Even here in New Zealand where we're still (sort of) under the
> King, no one here would consider not using the KJV, and we most
> certainly wouldn't be anticipating a court case if we used it in
> an app.
>
> I'm sure there's many silent listeners/readers/list-lurkers here
> like me who would find 1/ some of the views on copyright expressed
> earlier on the list very one-sided and out of character for an org
> like CrossWire, and 2/ find the secrecy even more out of
> character, and 3/ finding the UK-centric character of some of the
> discussion quite out of character for an org with so many
> international resources (and even for me in a British CommonWealth
> country it seems strangely narrow).
>
> Can the source text at least be passed to someone outside of the
> UK to place onto GitHub? I'll volunteer (or I'm sure many others
> would also).
>
> Let's get the Bible out to more people, and with more accuracy and
> more linked resources.
>
> Blessings,
> Robert Hunt
> Freely-Given.org
>
> On 17/01/23 10:01, Michael Johnson wrote:
>> On 1/16/23 06:23, David Haslam wrote:
>>>
>>> And yes - it remains the case that the text of the KJV is
>>> protected by Royal Letters Patent within the United Kingdom, and
>>> that in principle, this copyright assertion should be upheld by
>>> subsequent mutual treaties in those nations that were
>>> signatories of the Berne Convention.
>>
>> A minor correction with major implications: The KJV and Book of
>> Common Prayer Letters Patent are NOT a copyright with respect to
>> the Berne Convention. Those have no legal effect outside of the
>> UK. Full stop. BS/BFBS opinions notwithstanding. The latter
>> organization, and especially certain persons within them, have
>> already proven that it is willing to stretch copyright law to the
>> extent of committing copyfraud, so I don't trust their opinions.
>> Case in point: the Beaver Scriptures. One could also argue that
>> King James said nothing about digital copies, but only printing,
>> which is not necessarily a lame point. All REAL copyrights
>> expire. The term may exceed a lifetime, but they do expire.
>>
>> In the unlikely event that I wanted to print KJV Bibles and
>> import them into England or Wales, or if I wanted to print them
>> within those countries, I would care about the very old Letters
>> Patent about that. In no other case do they affect me or my Bible
>> distribution decisions. There is no evidence of anyone trying to
>> enforce those Letters Patent outside of England and Wales, except
>> perhaps in other parts of the UK, let alone succeeding. I have,
>> however, had a two Bible Societies challenge some texts I have
>> online. In one case, I produced written permission to share the
>> text. In the other, I produced evidence that the work was
>> permanently and irrevocably in the Public Domain. I'm very
>> careful about copyright law, and fully aware of its extreme
>> complexity in an international context. I'm also not intimidated
>> by copyfraud
>> <https://www.nyulawreview.org/issues/volume-81-number-3/copyfraud/>.
>>
>> --
>> signature
>>
>> Aloha,
>> */Michael Johnson/**
>> 26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
>> mljohnson.org <https://mljohnson.org/> • eBible.org
>> <https://eBible.org> • WorldEnglish.Bible
>> <https://WorldEnglish.Bible> • PNG.Bible <https://PNG.Bible>
>> Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
>> Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook:
>> fb.me/kahunapule <https://www.facebook.com/kahunapule>
>>
>>
>> _______________________________________________
>> sword-devel mailing list:sword-devel at crosswire.org
>> http://crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> _______________________________________________
> sword-devel mailing list:sword-devel at crosswire.org
> http://crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://crosswire.org/pipermail/sword-devel/attachments/20230122/908175a0/attachment.htm>
More information about the sword-devel
mailing list