<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Le 16/01/2023 à 22:34, Troy A.
Griffitts a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:11735690-1E9E-4161-82D8-245D35219EA8@crosswire.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hey guys. A few points of clarity.<br>
<br>
We do make the source available from our wiki page regarding the
work.<br>
<br>
<a href="https://wiki.crosswire.org/User:Dmsmith/KJV_2.6"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.crosswire.org/User:Dmsmith/KJV_2.6</a><br>
<br>
You will find a link to the source somewhere on that page.<br>
<br>
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.<br>
<br>
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!<br>
<br>
Troy <br>
</blockquote>
<br>
<br>
Hi,<br>
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. <br>
Troy do you intend to move in this direction?<br>
Or will this case drag on for years?<br>
<br>
Best regards, br Cyrille<br>
<br>
<br>
<blockquote type="cite"
cite="mid:11735690-1E9E-4161-82D8-245D35219EA8@crosswire.org"><br>
<div class="gmail_quote">On January 16, 2023 1:24:17 PM PST,
Robert Hunt <a class="moz-txt-link-rfc2396E" href="mailto:hunt.robertj@gmail.com"><hunt.robertj@gmail.com></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<p>Thanks Michael for that (although I haven't heard of the
Beaver Scriptures and my search engines gave no help).<br>
</p>
<p>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.</p>
<p>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).</p>
<p>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).<br>
</p>
<p>Let's get the Bible out to more people, and with more
accuracy and more linked resources.</p>
<p>Blessings,<br>
Robert Hunt<br>
Freely-Given.org<br>
</p>
<div class="moz-cite-prefix">On 17/01/23 10:01, Michael
Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ab2b8ebe-2430-a6e0-6099-b28eb54890d9@eBible.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">On 1/16/23 06:23, David Haslam
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:St9Jx9pEkgbKrjo1hUYakCFK3itMUh_2rkg-xTsVnrApivxVUd8FP0Xl-O_SHibW1JQa2mftOfmrpj_5BmU_JcOr1rJRAIeF1kvUc9731sU=@protonmail.com">
<div><br>
</div>
<div>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.</div>
</blockquote>
<p>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.<br>
</p>
<p>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 <a moz-do-not-send="true"
href="https://www.nyulawreview.org/issues/volume-81-number-3/copyfraud/">copyfraud</a>.<br>
</p>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=UTF-8">
<title>signature</title>
<p><font color="#000000">Aloha,<br>
<b><big><i>Michael Johnson</i></big></b></font><b><br>
<font color="#000070"> 26 HIWALANI LOOP • MAKAWAO HI
96768-8747</font></b><font color="#000070"> • USA<br>
<a href="https://mljohnson.org/"
moz-do-not-send="true">mljohnson.org</a> • <a
href="https://eBible.org" moz-do-not-send="true">eBible.org</a>
• <a href="https://WorldEnglish.Bible"
moz-do-not-send="true">WorldEnglish.Bible</a> • <a
href="https://PNG.Bible" moz-do-not-send="true">PNG.Bible</a><br>
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921<br>
Skype: kahunapule • Telegram/Twitter: @kahunapule • <a
href="https://www.facebook.com/kahunapule"
moz-do-not-send="true">Facebook: fb.me/kahunapule</a></font></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</blockquote>
</div>
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>