[sword-devel] BPBible 0.5.3 released

Hi all, BPBible 0.5.3 has been released. This is largely because of the move to Github, though it also contains a few bug-fixes. To see a list of the changes that have been included, look at http://www.bpbible.com/news/bpbible-0.5.3-changes Jon ___ sw

Re: [sword-devel] BPBible 0.5.3 released

Hi Jonathan, Please check the download link for the Portable edition, and correct if necessary. Currently it downloads the same setup file as the standard Windows edition. Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/BPBible-0-5-3-released-tp465

[sword-devel] thread-safety in libsword?

Hi, When accessing libsword simultaneously from multiple threads, it often crashes. When surrounding the calls to the library with a mutex.lock and a mutex.unlock at the end, there's no crashes when accessing it in the same situation. I am seeing this on Linux and on the Mac. Should I do something

Re: [sword-devel] BPBible 0.5.3 released

Thanks, David. Fixed. On Mon, Jan 11, 2016 at 11:06 PM, David Haslam wrote: > Hi Jonathan, > > Please check the download link for the Portable edition, and correct if > necessary. > > Currently it downloads the same setup file as the standard Windows edition. > > Best regards, > > David > > > >

Re: [sword-devel] thread-safety in libsword?

The library has no guarantees of multi-threaded safety, so you'll need to handle locking outside of the library. Out of curiosity: what types of simultaneous/multi-threaded calls are you performing? Some things can be parallelized by instantiating multiple instances of SWMgr (e.g. this is how Bibl

[sword-devel] Detecting bad references?

Either during the process towards module build (in which it's often necessary to fix xrefs) or even subsequently, is it feasible for SWORD to test a reference to a specified versification and to respond with whether the reference is good or bad? The question naturally follows on from my observatio

Re: [sword-devel] thread-safety in libsword?

True, use cases beyond module installation can not be solved by instantiating SWMgr per thread. There is ticked on bug tracker related to this issue http://www.crosswire.org/tracker/browse/API-166 Blessings. -Исходное сообщение- От: "Greg Hellings" Отправлено: ‎11.‎01.‎2016 18:05 Кому:

Re: [sword-devel] Detecting bad references?

I would second a report during module making. I would not support a report or refusal to work during normal function. Peter > Gesendet: Montag, 11. Januar 2016 um 15:52 Uhr > Von: "David Haslam" > An: sword-devel@crosswire.org > Betreff: [sword-devel] Detecting bad references? > > Either durin

Re: [sword-devel] Detecting bad references?

JSword compares references to Book, Chapter and Verse boundaries. We have a process that will extract references from a module and validate them. It may be broken as we don’t use it often. Its purpose is to validate that JSword can handle the references that it finds in a Bible or Commentary mod

Re: [sword-devel] thread-safety in libsword?

Hi Teus, Yes, as Greg has pointed out, we've done our best to make it easy to perform multitheaded operations with the library by allowing you to instantiate a new SWMgr for each thread. We don't use threading libraries ourself inside the engine to lock critical sections but instead we tried to

Re: [sword-devel] Detecting bad references?

The specific, short answer to your question is "no". At least, not within the engine. If you're actually checking an OsisID you could read the metadata and create a regex test for each versification. The more nuanced answer is that, when parsing a potential reference the engine will pop up as Reve

Re: [sword-devel] Detecting bad references?

These are just a few further thoughts in response to your speedy replies. I was assuming that the localised references have been parsed and converted to properly formed osisRef strings. What would be useful during the "fix xrefs" process is a means to perform a sanity check on these. i.e. One th

[sword-devel] 64 bit operating system support?

Are there any libraries used by SWORD that get compiled into PocketSword for which as yet there is no support for 64 bit hardware platforms? cf. From February this year, Apple will not accept any app updates that do not have 64 bit hardware support. If the answer is "yes", are any of these librar

Re: [sword-devel] 64 bit operating system support?

SWORD has no requirements on any library, to my knowledge. It has optional, recommended requirements of libcurl and ICU. Both of those support 64-bit. PocketSword's maintainer would have to specifically state whether or not he builds them into 64-bit packages. --Greg On Mon, Jan 11, 2016 at 10:32

Re: [sword-devel] Detecting bad references?

If you'd like to see if a VerseKey was normalized for a module's reference system, you can parse the reference with normalization off, and then with it on and compare the keys to see if they are the the same. vk2.setAutoNormalize(false); vk1.setText("1Sam.2.200"); vk2.setText("1Sam.2.200"); cout

Re: [sword-devel] Detecting bad references?

Thanks Troy. Is this something that Peter can easily incorporate within xreffix.pl ? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Detecting-bad-references-tp4655692p4655702.html Sent from the SWORD Dev mailing list archive at Nabble.com. __

Re: [sword-devel] Detecting bad references?

Thanks that makes sense. Peter > Gesendet: Montag, 11. Januar 2016 um 17:39 Uhr > Von: "Troy A. Griffitts" > An: "SWORD Developers' Collaboration Forum" > Betreff: Re: [sword-devel] Detecting bad references? > > If you'd like to see if a VerseKey was normalized for a module's > reference system

Re: [sword-devel] Category=Essays ?

All front-ends that support Raw GenBook support it. It is a label that is used on one Raw GenBook at CrossWire: Essays on The Good Samaritan: Violence on the Road, Social World of Bandits DM > On Jan 11, 2016, at 3:17 PM, David Haslam wrote: > > Are there any modules with Category=Essays ? >

Re: [sword-devel] Category=Essays ?

Thanks DM, Is the datapath the same as for GenBook ? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Category-Essays-tp4655704p4655706.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mai

Re: [sword-devel] Category=Essays ?

Datapaths are always relative to the root of the mods.d folder. By convention, essay data files would be stored in the same place as genbook and would need to follow the same rules. --Greg On Mon, Jan 11, 2016 at 2:34 PM, David Haslam wrote: > Thanks DM, > > Is the datapath the same as for GenBo

[sword-devel] Category=Essays ?

Are there any modules with Category=Essays ? Do any front-ends support this category ? cf. I observe that the category tree in Xiphos has no such branch. See also http://www.crosswire.org/wiki/DevTools:conf_Files#General_informatic_and_installer_elements David -- View this message in contex

Re: [sword-devel] Category=Essays ?

As Greg notes it is a convention and a rule. Rules: For all DataPaths they can be anything relative to the root of the shared storage location. That is they all start with “./“. For a Raw GenBook, the last part of the path is the filename without the suffix. That’s the rule for Raw GenBooks. A

Re: [sword-devel] Category=Essays ?

Yep! I installed the module straight after reading your earlier reply, so I began to understand better already. David PS. I've made some useful improvements to that wiki page. -- View this message in context: http://sword-dev.350566.n4.nabble.com/Category-Essays-tp4655704p4655709.html Sent f

[sword-devel] Latest version of libsword?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! What is the latest version? I'm getting warnings like The module "KorRV" requires a newer Sword library. Please update to "Sword 1.7.9". However, SWORD_VERSION in SVN seems to be 1.7.3, whereas Gentoo seems to have 1.7.4 and http://www.cr

Re: [sword-devel] Latest version of libsword?

1.7.4 is the latest. https://www.crosswire.org/svn/sword/tags/ Perhaps 1.7.9 was used to mean the head of current svn which will become 1.8 in many years. In which case it probably should have been set as 1.7.999 to fit with previous internal numbering. --Greg On Jan 11, 2016 4:16 PM, "Jaak Risti

Re: [sword-devel] Latest version of libsword?

I’d guess that someone was trying to change 1.5.9 to 1.7. — DM > On Jan 11, 2016, at 5:38 PM, Greg Hellings wrote: > > 1.7.4 is the latest. https://www.crosswire.org/svn/sword/tags/ > > Perhaps 1.7.9 was used to mean the head of current svn which will

Re: [sword-devel] BPBible 0.5.3 released

I have put a CrossWire website news item out. Peter On Tue, 2016-01-12 at 00:00 +1100, Jonathan Morgan wrote: > Thanks, David. > Fixed. > > On Mon, Jan 11, 2016 at 11:06 PM, David Haslam > wrote: > > Hi Jonathan, > > > > Please check the download link for the Portable edition, and > > correct

Re: [sword-devel] Latest version of libsword?

On Mon, 2016-01-11 at 16:38 -0600, Greg Hellings wrote: > 1.7.4 is the latest. https://www.crosswire.org/svn/sword/tags/ > Perhaps 1.7.9 was used to mean the head of current svn which will > become 1.8 in many years. In which case it probably should have been > set as 1.7.999 to fit with previous i

Re: [sword-devel] Latest version of libsword?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 $ git svn rebase Current branch master is up to date. $ git grep '1\.7\.3' CMakeLists.txt:SET(SWORD_VERSION 1.7.3) configure.ac:AC_INIT(sword, 1.7.3, sword-b...@crosswire.org, sword, http://crosswire.org/sword) include/swversion.h:#define SWORD_VERSI

Re: [sword-devel] Latest version of libsword?

I don't have commit privileges on all the necessary files on master. Rightfully the master branch should be indicating 1.8 prerelease. I only maintain the 1-7-x branch which should indicate 1.7.4. --Greg On Jan 11, 2016 5:05 PM, "Jaak Ristioja" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash:

Re: [sword-devel] Latest version of libsword?

http://www.crosswire.org/svn/sword/branches/sword-1-7-x/configure.ac 1.7.5 in prep for the next maintenance release. --Greg On Jan 11, 2016 5:08 PM, "Greg Hellings" wrote: > I don't have commit privileges on all the necessary files on master. > Rightfully the master branch should be indicating

Re: [sword-devel] thread-safety in libsword?

Hi, The ticket about thread safety exactly describes the problems I am seeing :) The code is this: sword::SWMgr manager (sword_logic_get_path ().c_str ()); sword::SWModule *module = manager.getModule (module_name.c_str ()); if (module) { string key = osis + " " + convert_to_string (cha

Re: [sword-devel] thread-safety in libsword?

Dear Teus, In what way are you accessing this code in a multi threaded fashion? Can you produce a small standalone program which exhibits the problem so we might debug? Thanks for your help improving things. Troy On January 12, 2016 12:14:56 AM MST, Teus Benschop wrote: >Hi, > >The ticket