Robin,
We appreciate your reports of issues. Anything not closed already is
not scheduled to be in 1.5.8.
Not, let me say a few things that might make you hopeful. Many of the
bugs you have reported do not belong under the SWORD module in our
bugtracker. Many of the issue that you mention
> I think examples and tests are less important, but
> we can see about adding projects for them also.
Your call ... I found the test\*.cpp files to be very helpful to
debug-step-around in the sword-api to figure out how it works. Other
than biblecs and search.cpp, there isn't sample code to learn
Greetings from California!
There seem to be over 40 open issues linked to Sword 1.5.6 on the Jira
bugtracker. How many and which of these issues will be closed in
1.5.8? Are the unresolved issues automatically transferred to the 1.5.8
defect list (or Affects version updated to 1.5.8) once
JH wrote:
The circumvention refered to by Jonathon and myself ...
That should have said "Jack and myself".
Jerry
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to uns
Jonathon Blake wrote:
Jack wrote:
Fortunately, I don't see circumvention in this case.
a) Zondervan, amongst other publishers does consider BIble Import
Tool to be a tool designed to circumvent their IP rights.
The circumvention refered to by Jonathon and myself
Jack Lewis wrote:
Fortunately, I don't see circumvention in this case. I see creating
comptability with other formats.
I have not looked closely at this specific case. My comment should be
taken as a general caution and may, or may not apply in this case.
Jerry
_
Leandro wrote:
> > The e-Sword license prohibits reverse engineering.
> Is such a prohibition legal anywhere in the world?
Yes.
xan
joanthon
--
A Fork requires:
Seven systems with:
1+ GHz Processors
2+ GB RAM
0.25 TB Hard drive space
_
Em Thu, 05 May 2005 23:47:13 +, Jonathon Blake escreveu:
> The e-Sword license prohibits reverse engineering.
Is such a prohibition legal anywhere in the world?
--
Leandro GuimarÃes Faria Corcete Dutra +55 (11) 5685 2219
mailto:[EMAIL PROTECTED]+55 (11) 5686 9607
http://br
Jack wrote:
> Fortunately, I don't see circumvention in this case.
a) Zondervan, amongst other publishers does consider BIble Import
Tool to be a tool designed to circumvent their IP rights.
b) Since the e-Sword modules are password protected, it is trivial to
demonstrate that converting them
JH wrote:
Jack Lewis wrote:
Disclaimer: IANAL.
Same here.
Reverse engeering for compatability is legal in the United States and
Europe. Examples include Samba, WINE, Accolade vs. Sega, Linux (from
UNIX), Kaffe (from Java). Here is some info:
As I understand it, (I have not looked into this
Jack Lewis wrote:
Disclaimer: IANAL.
Same here.
Reverse engeering for compatability is legal in the United States and
Europe. Examples include Samba, WINE, Accolade vs. Sega, Linux (from
UNIX), Kaffe (from Java). Here is some info:
As I understand it, (I have not looked into this in a while
I would love to have the new WHACD module to test in
Bibletime, as I am reading from the greek NT most days and
this module sounds much cleaner than the other accented
greek texts.
It also sounds like something I started working on, but only
got as far as Matthew with the little time i have ha
Hi guys
Just in case anyone thinks it is important, I think a bug
report I sent through a few weeks ago may have slipped
through the cracks.
The Bible Tool in Konqueror 3.4 had problems with accents
not showing up for the trial version of the WH greek text.
Both precomposed and the non precom
Hi there ...
Just to let you know that I got the old 'Cheatah' up and running and
linked with the latest build of the library. I will shortly be placing
the source and makefile for DevC++ where it can be downloaded and will
put a message on this list. The reasons for digging out and
resur
Hi all,
i am glad to anounce that the Theologische Inititative Freiburg has
decided to support OSIS-Fileformat in our API.
http://svn.berlios.de/viewcvs/ntssapi/trunk/
At first we will provide means for working on OSIS -Bible text, but
before we start this effort we need support from the SWORD
Will, that almost looks alright. The options are:
All Readings
Primary Reading
Secondary Reading
note the plural/singular difference.
You might want to just grab the available feature set and valid choices
from the engine, which is how most frontends (besides Bibletime :) ) use
the engine. Here
David,
I spent some time this weekend working on a few new features for our
web tools.
1) I've tried to make a semi-intelligent decision where to place the
popup box for language information.
2) The currenly selected word will have a shaded background
3) All words on the page from the same G
17 matches
Mail list logo
