[sword-devel] Remote Module Repository Wiki
Troy A. Griffitts
scribe at crosswire.org
Thu Nov 4 17:44:48 MST 2010
I just wanted to add that...
It is a huge part of our vision to have a broad number of publishers
host their own repositories of material for use with our software. We
do not seek out license deals with publishers like other Bible software
vendors do. We offer the ability for publishers to make their resources
available with minimal work on a vast number of platforms. This is our
selling point: no fees for us, minimal effort for them to publish their
We have spent countless hours developing our internal distributed
installation mechanism and our frontend developers have done a great job
exposing this beautifully to the end user, to work toward this becoming
a reality. It's been a long time in the works and now is finally
available in most all of our frontend applications.
Our primary goal has always been to make the Gospel of Christ as
available as possible to a lost world. Bible translations are
personally my highest priority, but publishers-- both commercial and
non-commercial-- have valuable resources for training the Body of
Christ. I would also like to see these resources become available for
Just wanted to share my heart on this matter.
On 11/05/2010 12:25 AM, Troy A. Griffitts wrote:
> Hey guys. We have been in talks with a number of Bible publishers (and
> SBL is approaching in just over a week where we hope to again pitch our
> software to even more publishers) and always point there to our wiki for
> technical details of running their own module repository:
> This page has a long history of edits by various individuals among whom
> I have only participated minimally.
> Is there any chance I can get some of you who have contributed to this
> valuable resource to clean it up a bit.
> I personally would like to see:
> its size reduced as small as possible to show how easy it is to run a
> remote repository. Initial, "simple repository" section greatly
> appreciated, but the rest is still a little cloudy for even me to
> important technical typos fixed (like mods.d.tar.g[z] fixed). Proper
> English sentences (sorry non-native speakers. I do value your input).
> it organized appropriately, with talks about having .zip files handy for
> people in persecuted countries and for mobile users without builtin
> installers (do we have any of these?) either moved to another page, as
> this has nothing to do with running a remote repository, or else moved
> to the end in a section explicitly delineated as not part of running a
> remote repository-- again, trying to make this task look very easy. I'm
> not saying this isn't valuable information, but I want these
> organizations to buy in for as little work possible.
> I hope you understand how this benefits the pitch.
> Thanks tons for your support,
> On 11/04/2010 10:55 PM, David Haslam wrote:
>> In the KJV module, there are 17 occurences of the alternative method to mark
>> translation changes.
>> <seg subType="x-added" type="x-transChange">...</seg>This alternative method
>> is a hack which seems to be required when the transChange text is within a
>> <w> container.
>> I assume that OSIS does not permit the recommended
>> <transChange>...</transChange> container element in such circumstances.
>> Xiphos 3.1.3 displays these without italics. This is a bug.
>> I have also observed that diatheke with RTF output_format does the same, so
>> perhaps the bug is in the SWORD API.
>> See also http://crosswire.org/wiki/OSIS_Bibles#Recommended_Approach
>> I have also reported the bug in the Xiphos tracker. ID=3103244.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel