You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
STEP Bible offers free offline installations. Which includes free legally obtained ESV, NIV, and other desirable modules in a local repository. In sword format, in a local sword repository.
I downloaded the debian package shows the repo to be at /opt/step/homes/sword/modules/texts/
Question
Is it possible to
point the local repository to this location instead?
seamlessly integrate a 2nd local repository without moving any of these files to the default local bibletime repo?
(for unix/linux/mac) set up static links to these files within the bible time repo?
Ethically and legally, reading the files from where they are installed from another program is not overstepping the license, but copying them moving them to another location might trigger actions by copyright holders (which likely would mean the modules are removed from STEP due to user abuse... which is not my goal.) Solutions I'm looking for make use of the StepBible repo where it is, hopefully without causing StepBible to see possibly incompatible files that BibleTime uses (i'm not sure Step reads all Sword formats... ie. they read OSIS, but I don't know if they read VPL, or GBF... as an example none of this tested.)
I don't have a lot of time, but will implement some solution like this locally and if possible update findings. This has been an ongoing request/issue with sword front ends since before BT existed... and it seems a legal way to access these versions is in sight. Automatic detection of existing repos and linking/redirection would make BT more usable for non-techies.
The text was updated successfully, but these errors were encountered:
(unix/linux/mac) Hard linking each file works. It wouldn't be that hard to shepherd these each boot or on a specific command (search system for other sword modules/repos..)
As a first step, try adding AugmentPath to your sword.conf file. I think that informs the SWORD library to look for modules in that additional path and add them to the current instance. It can appear multiple times in the file to add more paths.
Background
STEP Bible offers free offline installations. Which includes free legally obtained ESV, NIV, and other desirable modules in a local repository. In sword format, in a local sword repository.
https://www.stepbible.org/downloads.jsp
I downloaded the debian package shows the repo to be at /opt/step/homes/sword/modules/texts/
Question
Is it possible to
Ethically and legally, reading the files from where they are installed from another program is not overstepping the license, but copying them moving them to another location might trigger actions by copyright holders (which likely would mean the modules are removed from STEP due to user abuse... which is not my goal.) Solutions I'm looking for make use of the StepBible repo where it is, hopefully without causing StepBible to see possibly incompatible files that BibleTime uses (i'm not sure Step reads all Sword formats... ie. they read OSIS, but I don't know if they read VPL, or GBF... as an example none of this tested.)
I don't have a lot of time, but will implement some solution like this locally and if possible update findings. This has been an ongoing request/issue with sword front ends since before BT existed... and it seems a legal way to access these versions is in sight. Automatic detection of existing repos and linking/redirection would make BT more usable for non-techies.
The text was updated successfully, but these errors were encountered: