I was able to open http://crosswire.org/ftpmirror/pub/sword/utils/win32/
in Firefox, so unless the server is cached somewhere, I don't think it's
down.
I assume this the place you're enquiring about.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/FTP-server-mirro
Is the web mirror for the ftp server down?
Peter
Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to u
It would be very useful if the *Help | About* display for all SWORD
front-ends included a line to say which SWORD API version it was compiled
with.
This is common practice in many apps that use back-end / front-end
technology.
For JSword, a similar suggestion is equally valid.
Best regards,
Dav
Created a separate issue for the feature suppport to be moved into the API.
http://tracker.crosswire.org/browse/API-201
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656978.html
Sent from the SWORD Dev mailing list archive at N
The way the library handles versioning in our release strings makes it
non-trivial to keep the strings updated in SVN. The strings are correct in
the released tarball (e.g. it reports version 1.7.4).
--Greg
On Fri, Mar 17, 2017 at 9:43 AM, David Haslam wrote:
> Looks like someone goofed by not
Looks like someone goofed by not changing that string value!
i.e. SWORD 1.7.4 tells the world that it's only 1.7.3
Just created an issue in the tracker.
http://tracker.crosswire.org/browse/API-200
HT to Karl Kleinpaste for doing the search.
David
--
View this message in context:
http://
On 03/17/2017 08:15 AM, David Haslam wrote:
> With it not being an engine function (or so it seems)
I think this is a bug. (Ignoring JSword. Sword apps only.)
Seriously, if the conf has announced its acceptable level of support,
and the running instance of Sword is behind that, then Sword shouldn
Named footnote reference added for the JSword front-ends.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/ERV-issues-in-And-Bible-tp4656923p4656974.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
swo
JSword has never cared about the field. It represents what the SWORD engine can
and cannot handle. Rather it has a different mechanism. It examines each field
in the conf for unsupported values and marks those where it makes a difference
with “Unsupported”.
DM
> On Mar 17, 2017, at 8:15 AM, Da
With it not being an engine function (or so it seems), I have added a new row
here:
https://crosswire.org/wiki/Choosing_a_SWORD_program#Module_Management
Front-end developers, please supply your {{yes}} or {{no}} accordingly.
btw. Does JSword support MinimumVersion from the API or is it still do
On 03/17/2017 05:30 AM, David Haslam wrote:
> Do all front-ends behave in a similar manner, or are there some that ignore
> this item in the .conf file and just struggle on?
I had thought that it was an engine function, to disregard installed
modules whose MinimumVersion is beyond what the engine
The ERV module has *MinimumVersion=1.7.4*
I was hoping to be able to look at the ERV module in the IBT MK front-end,
but alas, all the *eBible.org* modules are incompatible with *xulsword*.
Here's what I see within *consoleLog.text* after I close the app.
ERROR: Dropping module "deu1912eb". engi
Just viewed ERV in PocketSword and observed that in 1 Chronicles 1, some of
the bullet points are on a separate line before the tagged verse text that
follows.
Verses 4, 24, 32 are OK.
Verses 5-23, 25-31, 33-50 are not, apart from the mid-verse items in some
verses.
Verses 51b-54 are OK as a si
13 matches
Mail list logo
