Re: [sword-devel] SWORD 1.7.0RC1 win32 utilities

2013-07-31 Thread David Haslam
To coincide with the full release (when it comes) of SWORD 1.7, this section of our wiki page ought to be updated to include these additional av11ns. http://crosswire.org/wiki/Alternate_Versification#Supported_versification_systems I'll gladly provide the editing effort, if Chris can supply an

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Mark Trompell
diatheke is broken probably beacuse of r2922. I try to revert to confirm... Btw, this change forces changes in xiphos and probably every other frontend. On Wed, Jul 31, 2013 at 4:24 AM, Troy A. Griffitts scr...@crosswire.org wrote: I understand apologies for the unacceptable delay will mean

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Mark Trompell
Ok, that's not because of r2922, but output of diatheke is crippled. On Wed, Jul 31, 2013 at 9:21 AM, Mark Trompell m...@foresightlinux.org wrote: diatheke is broken probably beacuse of r2922. I try to revert to confirm... Btw, this change forces changes in xiphos and probably every other

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Mark Trompell
I did some bisecting that shows r2921 is the first commit that breaks diatheke, so I think the revert of the qt support work wasn't complete On Wed, Jul 31, 2013 at 9:38 AM, Mark Trompell m...@foresightlinux.org wrote: Ok, that's not because of r2922, but output of diatheke is crippled. On

Re: [sword-devel] SWORD 1.7.0RC1 win32 utilities

2013-07-31 Thread Chris Little
Mostly, there's no good reason to distribute Win64 builds and there are a few good reasons not to. The only cases where 64-bit builds for Windows make any sense are: * when you completely control distribution and can be certain they won't be used on Win32 systems (as in the case of programs

Re: [sword-devel] SWORD 1.7.0RC1 win32 utilities

2013-07-31 Thread Chris Little
The new versifications at the moment are: Rahlfs LXX Orthodox SynodalProt But I'm considering removing Rahlfs (and will edit it otherwise). And LXX Orthodox may, with reasonably high probability, change in the next couple days. LXX is a versification for LXXs translations of LXXs. Orthodox

Re: [sword-devel] SWORD 1.7.0RC1 win32 utilities

2013-07-31 Thread David Haslam
Thanks Chris. I won't add these to the wiki page until the dust has settled and SWORD 1.7.0 is announced as a release. btw. Glad to read of SynodalProt. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/SWORD-1-7-0RC1-win32-utilities-tp4652941p4652949.html Sent

[sword-devel] v11n for CzeB21 ?

2013-07-31 Thread David Haslam
When module *CzeB21* was last built in July 2009, was it ever considered for an av11n? Has any thought been given to this since then? czeb21.conf has no v11n entry, so it assumes the default KJV, as indeed would be expected for all modules in CrossWire Main. CzeB21 emptyvss output looks like

[sword-devel] Transport status reporting

2013-07-31 Thread Jaak Ristioja
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Yesterday, I again found myself writing safety workarounds around Sword status reporting, i.e. for the sword::StatusReporter::statusUpdate() callback, which for some reason uses floating point doubles instead of integers. Digging my way into the

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Mark Trompell
attached patch makes diatheke somewhat work again. I wonder why the cast doesn't work. I tried this too, but doesn't help: diff --git a/include/swmodule.h b/include/swmodule.h index 16fb301..04dde03 100644 --- a/include/swmodule.h +++ b/include/swmodule.h @@ -47,7 +47,7 @@ class SWFilter;

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Troy A. Griffitts
Thanks Mark for the report. I've applied a different fix in diatheke which had an unsafe call to retain a pointer to temporary object. It just 'happened' to work previous. This was the reason for this signature change in the method-- to better advertise to developers that they shouldn't

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Mark Trompell
but your fix doesn't fix it... On Wed, Jul 31, 2013 at 1:51 PM, Troy A. Griffitts scr...@crosswire.org wrote: Thanks Mark for the report. I've applied a different fix in diatheke which had an unsafe call to retain a pointer to temporary object. It just 'happened' to work previous. This was

Re: [sword-devel] SWORD 1.7.0RC1

2013-07-31 Thread Troy A. Griffitts
OK, So, latest patch makes your test case valgrind clean. Thank you for the test case! diatheke -b KJV -f HTMLREF -k Ps 22.3 2 This patch fixes SWModule::operator const char *() but also deprecates it. Since we deprecated returning a const char * from renderText(), we shouldn't allow an

Re: [sword-devel] Transport status reporting

2013-07-31 Thread Troy A. Griffitts
Thanks for the report Jaak. This is excellent information. I appreciate you giving the benefit of the doubt to the original contributor and investigating why they might have made the method signature the way they did originally. That was gracious; that you. I've added the new method

Re: [sword-devel] German Elberfelder 1871 Bible module isn't authentic

2013-07-31 Thread David Haslam
See also http://de.wikipedia.org/wiki/Elberfelder_Bibel The section headed *Zeittafel zur Geschichte der Elberfelder Bibel* has a table of the versions history. David -- View this message in context:

Re: [sword-devel] Transport status reporting

2013-07-31 Thread Jaak Ristioja
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.07.2013 17:08, Troy A. Griffitts wrote: I've added the new method signature as you've suggested (slighted different to match the preStatus method), and deprecated the statusUpdate method. Oddly GCC doesn't warn me that I've overloaded the

Re: [sword-devel] Transport status reporting

2013-07-31 Thread Troy A. Griffitts
On 07/31/2013 04:40 PM, Jaak Ristioja wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.07.2013 17:08, Troy A. Griffitts wrote: I've added the new method signature as you've suggested (slighted different to match the preStatus method), and deprecated the statusUpdate method. Oddly