> Von: "Matěj Cepl"
> On Mon, 2014-02-24 at 16:49 -0700, Troy A. Griffitts wrote:
> > We DO MAINTAIN a link to the source where we obtained the material;
> > anyone wishing to use the data from one of our SWORD modules SHOULD
> > INSTEAD simply look at the source link in the module .conf file
On Mon, 2014-02-24 at 16:49 -0700, Troy A. Griffitts wrote:
> We DO MAINTAIN a link to the source where we obtained the material;
> anyone wishing to use the data from one of our SWORD modules SHOULD
> INSTEAD simply look at the source link in the module .conf file and use
> that source instead.
On Mon, 2014-02-24 at 22:00 -0600, Greg Hellings wrote:
>
>
> That said, I have no idea if Swig is compatible with Visual Studio,
> nor if there is a version available for running on Windows, nor if it
> would produce a DLL that would link happily on Windows against Python,
> nor how to install
Further to DM, crossconnect is the only project of which I am aware which in
recent years have tried to reimplement and actually got it off the ground.
Sharpsword was an attempt to create c# bindings. Like many previous attempts to
get to workings c# bindings it failed/was abandoned. Crossconne
Small correction: JSword is part of The SWORD Project and was created by
members of CrossWire Bible Society. We've also created SWIG and Corba bindings
so that the SWORD library is available in many contexts.
Many of the modules have been licensed to CrossWire for use by The SWORD
Project. Not
While it is possible to mix-and-match DLLs from Visual Studio with those
from MinGW or those from other compilers, it is not recommended as it
requires special work during the compiling and linking phase. It's rather
difficult. Thus, it would be easiest on you to build the bindings with the
same co
Regardless of what you want, the fact is that it's already to late.
JSword, sharpsword, CrossConnect and who knows what else already use
your format.
You are the authoritative source for other projects weather you like
it or not. The sword modules you have are an invaluable resource for
other proj
On Feb 24, 2014, at 5:59 PM, Stephan Kreutzer wrote:
>> The only module that we retain the text for is the KJV. I am the maintainer
>> for that source, and if you'd like it, just ask. It is freely available, but
>> I've not been very good on making it clear what is the most recent version.
>>
Jaak,
I hesitate to even humor yet another response to unwarranted criticism.
Let's just say what you really mean: You think people have trouble
contributing to the SWORD project because we don't use your choice of
source control software and because we have a very tight approval
process for
Historically, CrossWire has always maintained that our data formats are
volatile. We optimize them, add new features to them, basically change
them if we feel they need changing. In reality one could say that they
haven't changed much in the past few years, but this is only cursorily
true. T
To confirm what others have said: CrossWire has historically held the
position that we are not the keepers of any authoritative source
documents. There are a number of reasons for this, many have been
stated already in this thread: we are primarily a software development
project, other project
On Sunday, February 23, 2014 04:12:06 PM Kahunapule Michael Johnson wrote:
> ANY time you assume that poetry and prose markup neatly nest within verses,
> you WILL have problems if you process very many Bibles. Poetry lines are
> marked by (not ll) within , like:
Ah yes I was going from poor memo
I would like to make Python bindings to Sword. From reading the
documentation that comes with Sword, I see that I need to build the
entire Sword library in order to do this. What would be the
recommended compiler to use?
I am running Windows 8.1. I don't have any experience
On Mon, 2014-02-24 at 20:16 +, Peter von Kaehne wrote:
> I think the basic decision to not publish OSIS for texts we do not
> maintain is sound. I have disagreed with it in the past, but once I
> realised the Chinese whisper like deterioration of texts by project
> copying from project copying
I wonder if the fact that the sword module format is undocumented and
not published contributes to this perception. There are at least 4
different projects that I know of which implement sword module
support. And they have either had to look at the sword code and thus
accept GPL2 (no plus) licencin
On Mon, 2014-02-24 at 17:38 +0100, Matěj Cepl wrote:
> Although, the original message was IMHO completely trollish, there is
> one thing, where I would like to get a clarification.
>
> On Sun, 2014-02-23 at 22:21 -0800, Chris Little wrote:
> > We're not an OSIS document repository. Making XML docu
Title: signature
I understand the desire to have a
repository for Scripture source files that are freely
redistributable (i.e. public domain, Creative Commons, or
similar). I operate the beginnings of one at
https://Bible.cx/Scriptures/, and welcome additions. I d
Although, the original message was IMHO completely trollish, there is
one thing, where I would like to get a clarification.
On Sun, 2014-02-23 at 22:21 -0800, Chris Little wrote:
> We're not an OSIS document repository. Making XML documents available
> for that content that we could share is not
On Mon, 2014-02-24 at 17:38 +0100, Matěj Cepl wrote:
> removed (I am going to resend here the message I sent to David couple of
> weeks ago for which I have never received a reply). I would like to
Actually, it has been sent here as well …
http://article.gmane.org/gmane.comp.literature.sword.devel
Hi,
Jaak Ristioja wrote:
> In addition, although Sword is GPL, there are many obstacles for
> outsiders to actually start contributing to the project, hence I
> somewhat understand why Sword might be perceived as not Free
> software.
One of the freedoms of the GNU General Public License is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I must say that although I do not agree with all the criticism of the
Sword project I do agree with some of it, and I actually hope that a
bit of healthy competition would help both parties.
IMHO this again highlights some of the problems of the
21 matches
Mail list logo
