[sword-devel] Export of SWORD module bible text and user data into text documents

[Tobias Klein]

Thanks Peter!

I understand that a fine-grained mechanism for controlling the copyright 
rules is probably not a good idea.
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.

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".

On my machine this would apply to the following modules for example:

grep -r "DistributionLicense=Copyright" .

./nasgreek.conf:DistributionLicense=Copyrighted.
./bereanstrongsgreek.conf:DistributionLicense=Copyrighted; Permission 
granted to distribute non-commercially in SWORD format
./nashebrew.conf:DistributionLicense=Copyrighted.
./gerneue.conf:DistributionLicense=Copyrighted; Permission to distribute 
granted to CrossWire
./esv2001.conf:DistributionLicense=Copyrighted; Permission to distribute 
granted to CrossWire
./hebrewgreek.conf:DistributionLicense=Copyrighted; Free non-commercial 
distribution
./nasb.conf:DistributionLicense=Copyrighted; Permission to distribute 
granted to CrossWire
./engNET2016eb.conf:DistributionLicense=Copyrighted; Permission to 
distribute granted to eBible.org
./esv2011.conf:DistributionLicense=Copyrighted; Permission to distribute 
granted to Crosswire.  Strongs added by Tyndale House.
./na28.conf:DistributionLicense=Copyright DBG

So, based on this the based way to inform the user based on what's 
available right now would be:
If "Copyright" has been found in DistributionLicense display a dialogue 
when the user attempts to copy/export portions of the text.

Best regards,
Tobias

On 9/13/20 10:24 PM, refdoc at gmx.net wrote:
> I think what you try and discuss here are two separate matters. 
> Exporting and having some sort of grammar for encoding export 
> restrictions.
>
> 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.
>
> Xiphos adds some copyright warnings.
> c
> 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.
>
> 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"
>
> 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.
>
> I am not saying no, just these are my concerns
>
> Peter
>
>
>
>
> Sent from my mobile. Please forgive shortness, typos and weird 
> autocorrects.
>
>
> -------- Original Message --------
> Subject: [sword-devel] Export of SWORD module bible text and user data 
> into text documents
> From: Tobias Klein
> To: SWORD Developers' Collaboration Forum
> CC:
>
>
>     Hi,
>
>     I've been thinking about the use case of exporting bible text in
>     combination with user data (notes, tags, etc.).
>
>     This is a normal use case in the context of bible study,
>     especially for
>     preparing sermons and/or bible study material.
>
>     I realize that translations like the NASB have rules that for
>     example do
>     not allow to export a complete book, only  a certain number of
>     verses etc.
>
>     Would it be possible to "codify" these rules in the SWORD module
>     files?
>     In this case the frontends could detect what's allowed for specific
>     modules and offer the user export functionality based on that.
>
>     My specific use case would be the following:
>
>     Export a word document containing the entire text of a book in a
>     table:
>
>     1st column: Verse Reference
>     2nd column: Verse text
>     3rd column: Tags
>     4th column: User notes
>
>     I realize that this may be a controversial topic. Nevertheless I do
>     think it is an important use case.
>
>     Thoughts?
>
>     Best regards,
>     Tobias
>
>     _______________________________________________
>     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
>
>
> _______________________________________________
> 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/20200914/e5cca8ef/attachment.html>