According to http://crosswire.org/wiki/Osis2mod#History_of_Changes
the latest version of osis2mod is *r2693* dated 2012-03-24.
When I just examined http://crosswire.org/ftpmirror/pub/sword/utils/win32/
the latest available version of Sword utilities compiled for Windows is
I made a release which I sent you the link to back in the spring when
I was building for Xiphos. I don't remember the exact revision number,
but it would have been dated sometime to February.
Also, the versions of the utilities released with Xiphos would be the
same as the ones released in
Thanks Greg,
I have *xiphos.exe 3.1.5-webkit* and the Xiphos folder does indeed contain
most of the utilities.
If I run osis2mod.exe from there, the revision number is just displayed as
*$Rev$* (without an r-number) so it doesn't exactly show which SWORD release
it was.
All the filedates are
If you see $Rev$, then SVN was not used to do the checkout of the file.
The date is indicative of the build and presumably of the checkout. Typically,
a developer will get all the current files before doing a build.
You can use the command svn log to get a history of the file and you can
On Tue, Oct 23, 2012 at 7:42 AM, David Haslam dfh...@googlemail.com wrote:
Thanks Greg,
I have *xiphos.exe 3.1.5-webkit* and the Xiphos folder does indeed contain
most of the utilities.
If I run osis2mod.exe from there, the revision number is just displayed as
*$Rev$* (without an r-number)
Thanks DM,
All bets are off is a good summary of the current situation for Win32
users like me.
Anything more recent than *r2563* is a total mess as far as I'm concerned.
/That might seem extreme, but it aptly expresses my frustration./
OK - this is what I've done.
* I tweaked the USFM to
When the sword Rev changes, I manually edit the osis2mod.cpp so that it
reflects the sword version. That way when I run osis2mod it reports the
current sword version, not the last unchanged osis2mod version.
It's an easy fix if that's of help.
~A
On Tuesday, October 23, 2012, David Haslam
