<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks Peter!</p>
<p>I understand that a fine-grained mechanism for controlling the
copyright rules is probably not a good idea.<br>
However, it could be at least a "boolean option", right? The conf
file could indicate whether there is some copyright protection or
not. And this could be the basis for displaying a message before
allowing the user to export a document.</p>
<p>I just checked the conf files. The implicit way of checking
whether a module is copyrighted would be scanning the
"DistributionLicense" field for the term "Copyright".</p>
<p>On my machine this would apply to the following modules for
example:</p>
<p><tt>grep -r "DistributionLicense=Copyright" .</tt></p>
<p><tt>./nasgreek.conf:DistributionLicense=Copyrighted.</tt><tt><br>
</tt><tt>./bereanstrongsgreek.conf:DistributionLicense=Copyrighted;
Permission granted to distribute non-commercially in SWORD
format</tt><tt><br>
</tt><tt>./nashebrew.conf:DistributionLicense=Copyrighted.</tt><tt><br>
</tt><tt>./gerneue.conf:DistributionLicense=Copyrighted;
Permission to distribute granted to CrossWire</tt><tt><br>
</tt><tt>./esv2001.conf:DistributionLicense=Copyrighted;
Permission to distribute granted to CrossWire</tt><tt><br>
</tt><tt>./hebrewgreek.conf:DistributionLicense=Copyrighted; Free
non-commercial distribution</tt><tt><br>
</tt><tt>./nasb.conf:DistributionLicense=Copyrighted; Permission
to distribute granted to CrossWire</tt><tt><br>
</tt><tt>./engNET2016eb.conf:DistributionLicense=Copyrighted;
Permission to distribute granted to eBible.org</tt><tt><br>
</tt><tt>./esv2011.conf:DistributionLicense=Copyrighted;
Permission to distribute granted to Crosswire. Strongs added by
Tyndale House.</tt><tt><br>
</tt><tt>./na28.conf:DistributionLicense=Copyright DBG</tt><tt><br>
</tt></p>
<p>So, based on this the based way to inform the user based on
what's available right now would be:<br>
If "Copyright" has been found in DistributionLicense display a
dialogue when the user attempts to copy/export portions of the
text.<br>
</p>
<p>Best regards,<br>
Tobias</p>
<div class="moz-cite-prefix">On 9/13/20 10:24 PM, <a class="moz-txt-link-abbreviated" href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:-2sc6bp-7fcyfx-4n21d8-1mxthk-56v8rkw6tmc1-p1swml-ffboya-ytekv6u1g4nf-snsr03-hmrmbk-f53dxi-4u498n-jjei2i5wai1a-1zoy951vpvec-9zof54su6kyd9utyn6-tvunrj-mkzwz3hlgomg.1600028666435@email.android.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I think what you try and discuss here are two separate matters.
Exporting and having some sort of grammar for encoding export
restrictions. <br>
<br>
Most front-end have some sort of copy paste mechanism, share
mechanism or else. Mobile ones go.more for share while desktop
ones go.more for export. <br>
<br>
Xiphos adds some copyright warnings. <br>
c<br>
What you want though is more elaborate in terms of
warning/restriction. Some of it is hard to encode, some of it may
be easier. The problem is that each restriction set might be very
disparate and not just in percentages. <br>
<br>
A simple one might read "not more than 100 verses" a complex one
might be "not more than half of a book, no whole chapter and not
more than 200 verses in total, and not more than 10% of the final
document"<br>
<br>
I think once you start, you need to either cover all kinds of edge
cases we never thought about or you risk anger from publishers who
suddenly like that kind of electronic restriction. And then there
is the fact that it is easy to override. <br>
<br>
I am not saying no, just these are my concerns<br>
<br>
Peter<br>
<br>
<br>
<br>
<br>
Sent from my mobile. Please forgive shortness, typos and weird
autocorrects.
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="quote" style="line-height: 1.5"><br>
<br>
-------- Original Message --------<br>
Subject: [sword-devel] Export of SWORD module bible text and
user data into text documents<br>
From: Tobias Klein <contact@tklein.info><br>
To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org><br>
CC: <br>
<br>
<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I've been thinking about the use case of exporting bible
text in <br>
combination with user data (notes, tags, etc.).<br>
<br>
This is a normal use case in the context of bible study,
especially for <br>
preparing sermons and/or bible study material.<br>
<br>
I realize that translations like the NASB have rules that
for example do <br>
not allow to export a complete book, only a certain
number of verses etc.<br>
<br>
Would it be possible to "codify" these rules in the SWORD
module files? <br>
In this case the frontends could detect what's allowed for
specific <br>
modules and offer the user export functionality based on
that.<br>
<br>
My specific use case would be the following:<br>
<br>
Export a word document containing the entire text of a
book in a table:<br>
<br>
1st column: Verse Reference<br>
2nd column: Verse text<br>
3rd column: Tags<br>
4th column: User notes<br>
<br>
I realize that this may be a controversial topic.
Nevertheless I do <br>
think it is an important use case.<br>
<br>
Thoughts?<br>
<br>
Best regards,<br>
Tobias<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above
page</blockquote>
</sword-devel@crosswire.org></contact@tklein.info></div>
<br>
<fieldset class="mimeAttachmentHeader"></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>
</body>
</html>