From niccarter at mac.com Tue Jan 1 18:11:35 2013 From: niccarter at mac.com (Nic Carter) Date: Wed, 02 Jan 2013 12:11:35 +1100 Subject: [sword-devel] filter patch In-Reply-To: References: Message-ID: <4A2C007D-0C5C-448D-BE9D-EE7C5AA79FF5@mac.com> A search of the PS source code for "¶" reveals no hits. Search of the current libsword that PS uses also reveals no hits. I believe PS only shows pilcrows for those modules that have them inside, such as KJV. FYI, there is a fun comment in our display code that says: // paragraphing can be annoying, as different module creators can do things differently! And it sums up my thoughts with paragraphs in the filter code & individual modules... ;) I'm about to do a new release of PS that tries to clean up the rather messy paragraphing in some certain modules (such as the ESV!)... [It's just been submitted & so hopefully will be live within a week?] For example, it is not uncommon to find the following 3 situations in the produced HTML that the filters give me: "


" or "


" or "


" *sigh* On 15/12/2012, at 12:34 AM, Karl Kleinpaste wrote: > I think it's pretty clear that all of this sort of processing belongs in > the filter, not in the apps at all, and that if pilcrows (¶) are > desired, they too should be part of the filter-provided stream. > > Do other apps generate pilcrows, or is this a GnomeSword/Xiphos-specific > oddity? > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From niccarter at mac.com Tue Jan 1 19:06:33 2013 From: niccarter at mac.com (Nic Carter) Date: Wed, 02 Jan 2013 13:06:33 +1100 Subject: [sword-devel] XHTML and Khmer In-Reply-To: <89548483-8955-441A-8865-26040CAE65E6@me.com> References: <89548483-8955-441A-8865-26040CAE65E6@me.com> Message-ID: On 20/12/2012, at 7:06 AM, Manfred Bergmann wrote: > a) what are the XHtml filters. What are they for? Do they do anything different than the HtmlHref filters? Don't think anyone answered this question? Right now they're almost exactly the same. The idea is that these can be hacked to do things more properly rather than the horrid html that is produced by the htmlhref filters... Almost like a fresh start, altho not much has been changed so far. Ideally they should produce loads of html code with classes for all the display markup (such as ), rather than using loads of markup elements (such as ) which is what we currently do... Why bother with all those markup elements AND using classes, when using appropriate classes would make the use of the markup irrelevant? :/ Compare my hacked version of osishtmlhref.ccp:67 at https://bitbucket.org/niccarter/pocketsword/src/74e571ae219c821e1aaf9764d8c43ae7b52ffb9f/externals/sword/src/modules/filters/osishtmlhref.cpp?at=default#cl-67 to the equivalent line in osisxhtml.cpp:79 But I am hoping that the xhtml filters will be properly updated and work will be done to validate the xhtml output. ;) I would have tried this long ago, but I gather there is too much attachment with the filters for any one front-end to attempt to change them? hence my fork of the htmlhref filters for use in PS. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From niccarter at mac.com Tue Jan 1 20:27:57 2013 From: niccarter at mac.com (Nic Carter) Date: Wed, 02 Jan 2013 14:27:57 +1100 Subject: [sword-devel] Beta modules question Message-ID: Heya all, Just a quick question about beta modules. Currently we have the wiki page that is meant to be where we "report" problems. I have been emailed again about the Barnes Notes module and looking at the entry for it on the wiki at http://crosswire.org/wiki/Modules_in_the_beta_repository#Commentary_Modules shows that the reported issues I was emailed are already on that wiki page. Looking at the conf file for the module doesn't let me know the source of the text, and so there is nothing I can do to look into the problems reported. My suggestion is that perhaps we should remove modules from the beta repo that are not going to be updated? It has been 5 years since that module was "updated" and these bugs in the module have been noted at several points on the wiki since then, including in 2008, 2009 & 2012 (observed via a very quick search of the history of that wiki page). Alternatively, for this module a quick re-encoding as UTF-8 would fix the most noticeable problem ;) Thanks heaps, ybic nic... :) From niccarter at mac.com Wed Jan 2 00:22:56 2013 From: niccarter at mac.com (Nic Carter) Date: Wed, 02 Jan 2013 18:22:56 +1100 Subject: [sword-devel] Patches to fix compiler warnings In-Reply-To: <50D3A00E.8060909@ristioja.ee> References: <50D3A00E.8060909@ristioja.ee> Message-ID: Thanks for these. Hopefully some kind soul will apply them? For those who are interested, some fun articles related to this stuff: * http://inessential.com/2012/12/31/coders_in_the_hands_of_an_angry_god * http://boredzo.org/blog/archives/2009-11-07/warnings * (more appropriate to Obj-C) http://ashfurrow.com/blog/seven-deadly-sins-of-modern-objective-c :) On 21/12/2012, at 10:32 AM, Jaak Ristioja wrote: > Please apply these patches (bzip2-ed to workaround sword-devel 90 KB > message size limit and attached) to fix about 3000 compiler warnings > with GCC and Clang. From dfhmch at googlemail.com Wed Jan 2 03:09:01 2013 From: dfhmch at googlemail.com (David Haslam) Date: Wed, 2 Jan 2013 02:09:01 -0800 (PST) Subject: [sword-devel] filter patch In-Reply-To: <4A2C007D-0C5C-448D-BE9D-EE7C5AA79FF5@mac.com> References: <4A2C007D-0C5C-448D-BE9D-EE7C5AA79FF5@mac.com> Message-ID: <1357121341003-4651499.post@n4.nabble.com> Aside: xulsword modules don't use OSIS elements

and

for paragraphs. The developer would probably agree with Nic's comment! // paragraphing can be annoying, as different module creators can do things differently! xulsword modules just make use of to provide the line breaks for where "paragraphs" end. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/filter-P-patch-tp4651388p4651499.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Wed Jan 2 03:17:24 2013 From: dfhmch at googlemail.com (David Haslam) Date: Wed, 2 Jan 2013 02:17:24 -0800 (PST) Subject: [sword-devel] Beta modules question In-Reply-To: References: Message-ID: <1357121844291-4651500.post@n4.nabble.com> When beta modules don't get corrected for years, it's probably because other matters have much higher priority, and most CrossWire volunteers have a day-job or other full-time commitments. cf. Those of us who are retired are few and far between. Would it not be feasible to correct the *Barnes* commentary module by using mod2imp, edit the output IMP file, and then rebuild using imp2vs ? Or am I being too simplistic? HNY! David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Beta-modules-question-tp4651497p4651500.html Sent from the SWORD Dev mailing list archive at Nabble.com. From refdoc at gmx.net Wed Jan 2 03:25:52 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Wed, 02 Jan 2013 10:25:52 +0000 Subject: [sword-devel] Beta modules question In-Reply-To: <1357121844291-4651500.post@n4.nabble.com> References: <1357121844291-4651500.post@n4.nabble.com> Message-ID: <50E40B30.4040705@gmx.net> On 02/01/13 10:17, David Haslam wrote: > Would it not be feasible to correct the *Barnes* commentary module by using > mod2imp, edit the output IMP file, and then rebuild using imp2vs ? > I have not tried it, but I would think this might massively increase the size of a module with verse ranges as a commentary is likely to have - each verse will be given its own mirrored entry, many times in row. Peter From dfhmch at googlemail.com Wed Jan 2 03:34:57 2013 From: dfhmch at googlemail.com (David Haslam) Date: Wed, 2 Jan 2013 02:34:57 -0800 (PST) Subject: [sword-devel] Beta modules question In-Reply-To: <50E40B30.4040705@gmx.net> References: <1357121844291-4651500.post@n4.nabble.com> <50E40B30.4040705@gmx.net> Message-ID: <1357122897586-4651502.post@n4.nabble.com> I see from my facebook feeds that Illya Antonenko (osnova.com) has recently published Barnes as a Kindle edition (& for other e-book platforms too). He generally uses OSIS, so he must have made or edited an OSIS source file for Barnes. Being friendly disposed towards CrossWire, it may be worth asking him for access to his XML file, so that our beta module can be corrected and improved. Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Beta-modules-question-tp4651497p4651502.html Sent from the SWORD Dev mailing list archive at Nabble.com. From niccarter at mac.com Wed Jan 2 19:01:53 2013 From: niccarter at mac.com (Nic Carter) Date: Thu, 03 Jan 2013 13:01:53 +1100 Subject: [sword-devel] ISV status? Message-ID: Hi Team :) I was wondering where we were at with updating the ISV to include both the OT & NT? There was some chatter here about a year ago about it, but it sounded yuck, given we needed to convert the text from a Word document... :/ Thanks, ybic nic... :) From chrislit at crosswire.org Thu Jan 3 00:28:10 2013 From: chrislit at crosswire.org (Chris Little) Date: Wed, 02 Jan 2013 23:28:10 -0800 Subject: [sword-devel] Beta modules question In-Reply-To: References: Message-ID: <50E5330A.9060905@crosswire.org> On 1/1/2013 7:27 PM, Nic Carter wrote: > > Heya all, > > Just a quick question about beta modules. > Currently we have the wiki page that is meant to be where we "report" problems. I have been emailed again about the Barnes Notes module and looking at the entry for it on the wiki at http://crosswire.org/wiki/Modules_in_the_beta_repository#Commentary_Modules shows that the reported issues I was emailed are already on that wiki page. > Looking at the conf file for the module doesn't let me know the source of the text, and so there is nothing I can do to look into the problems reported. > > My suggestion is that perhaps we should remove modules from the beta repo that are not going to be updated? It has been 5 years since that module was "updated" and these bugs in the module have been noted at several points on the wiki since then, including in 2008, 2009 & 2012 (observed via a very quick search of the history of that wiki page). > Alternatively, for this module a quick re-encoding as UTF-8 would fix the most noticeable problem ;) At this point, I wouldn't recommend directing users to download from the beta repository. We don't release new content to beta any longer and the content that was reasonably good has long been moved to other repositories. So the content remaining in beta is either fairly broken, relies on features not well-supported by front ends, or has been orphaned because whoever is responsible is no longer contributing to the project. I've removed Barnes and am working on a replacement right now, having found a reasonably good source text. The existing module was badly malformed and not a candidate for simple re-encoding & recompiling. --Chris From niccarter at mac.com Thu Jan 3 05:03:57 2013 From: niccarter at mac.com (Nic Carter) Date: Thu, 03 Jan 2013 23:03:57 +1100 Subject: [sword-devel] Beta modules question In-Reply-To: <50E5330A.9060905@crosswire.org> References: <50E5330A.9060905@crosswire.org> Message-ID: <9B4337E8-D000-424A-BDBE-0104E7F1EA87@mac.com> On 03/01/2013, at 6:28 PM, Chris Little wrote: > At this point, I wouldn't recommend directing users to download from the beta repository. We don't release new content to beta any longer and the content that was reasonably good has long been moved to other repositories. So the content remaining in beta is either fairly broken, relies on features not well-supported by front ends, or has been orphaned because whoever is responsible is no longer contributing to the project. This is an interesting recommendation, as our MasterRepoList.conf lists it as one of our main module repositories!!! http://crosswire.org/ftpmirror/pub/sword/masterRepoList.conf Can I again please ask that we remove Repos from that list that are not for general public use, such as the attic repos? On the one hand we have been provided with the API to easily access this "master list" for our users to quickly and easily update their installations of their SWORD front-end to the latest and greatest repositories for modules, but on the other hand, we are being told not to recommend users actually use some of them? Clarification in this area would be brilliant. :) Thanks heaps, ybic nic... :) From chrislit at crosswire.org Thu Jan 3 06:04:50 2013 From: chrislit at crosswire.org (Chris Little) Date: Thu, 03 Jan 2013 05:04:50 -0800 Subject: [sword-devel] Beta modules question In-Reply-To: <9B4337E8-D000-424A-BDBE-0104E7F1EA87@mac.com> References: <50E5330A.9060905@crosswire.org> <9B4337E8-D000-424A-BDBE-0104E7F1EA87@mac.com> Message-ID: <50E581F2.3070209@crosswire.org> On 1/3/2013 4:03 AM, Nic Carter wrote: > > On 03/01/2013, at 6:28 PM, Chris Little wrote: > >> At this point, I wouldn't recommend directing users to download from the beta repository. We don't release new content to beta any longer and the content that was reasonably good has long been moved to other repositories. So the content remaining in beta is either fairly broken, relies on features not well-supported by front ends, or has been orphaned because whoever is responsible is no longer contributing to the project. > > This is an interesting recommendation, as our MasterRepoList.conf lists it as one of our main module repositories!!! > http://crosswire.org/ftpmirror/pub/sword/masterRepoList.conf > > Can I again please ask that we remove Repos from that list that are not for general public use, such as the attic repos? The only repository not for general public use is not listed in masterRepoList.conf, and that's the experimental repository. The attic repositories are definitely intended for the public to use. If users care to, they can downgrade from a broken module (for example) from the attic repositories. > On the one hand we have been provided with the API to easily access this "master list" for our users to quickly and easily update their installations of their SWORD front-end to the latest and greatest repositories for modules, > but on the other hand, we are being told not to recommend users actually use some of them? > > Clarification in this area would be brilliant. :) I would suggest that you quit presenting CrossWire Beta as "CrossWire 2". I know Apple doesn't want 'beta' showing up in the delivered app, but I presume you can sidestep this by loading from masterRepoList.conf. Calling the beta repository "CrossWire 2" obscures the fact that this content is intentionally segregated from our main repositories due to issues such as lacking quality. Indeed, I would suggest that (if you don't want to load all of the repositories from masterRepoList.conf the first time a user goes to download a module) you pre-load just the main repository and maybe av11n. And I'd recommend keeping the repository names as they appear in masterRepoList.conf--having two copies of the av11n repository is annoying and could be confusing to users. --Chris From thulester at gmail.com Thu Jan 3 10:37:33 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 12:37:33 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: I believe there's an OSIS file that contains both testaments ... I can forward it if it helps this effort. There are least two versification problems (I haven't bothered to address yet) INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content to 1Sam.10.27 INFO(V11N): Rev.13 is not in the KJV versification. Appending content to Rev.12.17 I've placed a mod based on this OSIS file in my repo if anyone interested: Repository: 1XO Host: ftp.1xo.net /1xo/pub/sword/betaraw ~A On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter wrote: > > Hi Team :) > > I was wondering where we were at with updating the ISV to include both the > OT & NT? > There was some chatter here about a year ago about it, but it sounded > yuck, given we needed to convert the text from a Word document... :/ > > Thanks, ybic > nic... :) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Thu Jan 3 10:44:59 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Thu, 03 Jan 2013 17:44:59 +0000 Subject: [sword-devel] Beta modules question In-Reply-To: <50E581F2.3070209@crosswire.org> References: <50E5330A.9060905@crosswire.org> <9B4337E8-D000-424A-BDBE-0104E7F1EA87@mac.com> <50E581F2.3070209@crosswire.org> Message-ID: <50E5C39B.5030302@gmx.net> On 03/01/13 13:04, Chris Little wrote: > > I would suggest that you quit presenting CrossWire Beta as "CrossWire > 2". I know Apple doesn't want 'beta' showing up in the delivered app, > but I presume you can sidestep this by loading from masterRepoList.conf. I would second that. Beta was meant to be used by more people than just the core, simply because we do not have the resources to check. But users should know and accept that while it might be great it could also be buggy. Peter From chrislit at crosswire.org Thu Jan 3 11:28:15 2013 From: chrislit at crosswire.org (Chris Little) Date: Thu, 03 Jan 2013 10:28:15 -0800 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: <50E5CDBF.8080508@crosswire.org> Andrew, this document is copyrighted. We do not have permission to distribute it. You certainly and absolutely do not have permission to distribute it, much less to distribute it and claim that we have permission to distribute it. Remove it immediately. --Chris On 1/3/2013 9:37 AM, Andrew Thule wrote: > I believe there's an OSIS file that contains both testaments ... I can > forward it if it helps this effort. > > There are least two versification problems (I haven't bothered to > address yet) > INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content > to 1Sam.10.27 > INFO(V11N): Rev.13 is not in the KJV versification. Appending content to > Rev.12.17 > > I've placed a mod based on this OSIS file in my repo if anyone interested: > Repository: 1XO > Host: ftp.1xo.net > /1xo/pub/sword/betaraw > > ~A > > > On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter > wrote: > > > Hi Team :) > > I was wondering where we were at with updating the ISV to include > both the OT & NT? > There was some chatter here about a year ago about it, but it > sounded yuck, given we needed to convert the text from a Word > document... :/ > > Thanks, ybic > nic... :) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From thulester at gmail.com Thu Jan 3 11:53:24 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 13:53:24 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <50E5CDBF.8080508@crosswire.org> References: <50E5CDBF.8080508@crosswire.org> Message-ID: Done. I made it available here only in response to this request .. ~A On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: > Andrew, this document is copyrighted. We do not have permission to > distribute it. You certainly and absolutely do not have permission to > distribute it, much less to distribute it and claim that we have permission > to distribute it. > > Remove it immediately. > > --Chris > > > > On 1/3/2013 9:37 AM, Andrew Thule wrote: > >> I believe there's an OSIS file that contains both testaments ... I can >> forward it if it helps this effort. >> >> There are least two versification problems (I haven't bothered to >> address yet) >> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >> to 1Sam.10.27 >> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to >> Rev.12.17 >> >> I've placed a mod based on this OSIS file in my repo if anyone interested: >> Repository: 1XO >> Host: ftp.1xo.net >> >> /1xo/pub/sword/betaraw >> >> ~A >> >> >> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter > > wrote: >> >> >> Hi Team :) >> >> I was wondering where we were at with updating the ISV to include >> both the OT & NT? >> There was some chatter here about a year ago about it, but it >> sounded yuck, given we needed to convert the text from a Word >> document... :/ >> >> Thanks, ybic >> nic... :) >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> > >> >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 11:56:13 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 13:56:13 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E5CDBF.8080508@crosswire.org> Message-ID: I guess that answers the question posed by Nic then .. These efforts are apparently on hold pending permission to distribute. ~A On Thu, Jan 3, 2013 at 1:53 PM, Andrew Thule wrote: > Done. > > I made it available here only in response to this request .. > > ~A > > > On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: > >> Andrew, this document is copyrighted. We do not have permission to >> distribute it. You certainly and absolutely do not have permission to >> distribute it, much less to distribute it and claim that we have permission >> to distribute it. >> >> Remove it immediately. >> >> --Chris >> >> >> >> On 1/3/2013 9:37 AM, Andrew Thule wrote: >> >>> I believe there's an OSIS file that contains both testaments ... I can >>> forward it if it helps this effort. >>> >>> There are least two versification problems (I haven't bothered to >>> address yet) >>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >>> to 1Sam.10.27 >>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to >>> Rev.12.17 >>> >>> I've placed a mod based on this OSIS file in my repo if anyone >>> interested: >>> Repository: 1XO >>> Host: ftp.1xo.net >>> >>> /1xo/pub/sword/betaraw >>> >>> ~A >>> >>> >>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >> > wrote: >>> >>> >>> Hi Team :) >>> >>> I was wondering where we were at with updating the ISV to include >>> both the OT & NT? >>> There was some chatter here about a year ago about it, but it >>> sounded yuck, given we needed to convert the text from a Word >>> document... :/ >>> >>> Thanks, ybic >>> nic... :) >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> > >>> >>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 12:07:31 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 14:07:31 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E5CDBF.8080508@crosswire.org> Message-ID: Once (if?) you obtain permission to distribute, please let the list know so that volunteers can continue to move this effort forward. (Conversion from a Word document may no longer be necessary). ~A On Thu, Jan 3, 2013 at 1:56 PM, Andrew Thule wrote: > I guess that answers the question posed by Nic then .. > > These efforts are apparently on hold pending permission to distribute. > ~A > > > > On Thu, Jan 3, 2013 at 1:53 PM, Andrew Thule wrote: > >> Done. >> >> I made it available here only in response to this request .. >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: >> >>> Andrew, this document is copyrighted. We do not have permission to >>> distribute it. You certainly and absolutely do not have permission to >>> distribute it, much less to distribute it and claim that we have permission >>> to distribute it. >>> >>> Remove it immediately. >>> >>> --Chris >>> >>> >>> >>> On 1/3/2013 9:37 AM, Andrew Thule wrote: >>> >>>> I believe there's an OSIS file that contains both testaments ... I can >>>> forward it if it helps this effort. >>>> >>>> There are least two versification problems (I haven't bothered to >>>> address yet) >>>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >>>> to 1Sam.10.27 >>>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to >>>> Rev.12.17 >>>> >>>> I've placed a mod based on this OSIS file in my repo if anyone >>>> interested: >>>> Repository: 1XO >>>> Host: ftp.1xo.net >>>> >>>> /1xo/pub/sword/betaraw >>>> >>>> ~A >>>> >>>> >>>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >>> > wrote: >>>> >>>> >>>> Hi Team :) >>>> >>>> I was wondering where we were at with updating the ISV to include >>>> both the OT & NT? >>>> There was some chatter here about a year ago about it, but it >>>> sounded yuck, given we needed to convert the text from a Word >>>> document... :/ >>>> >>>> Thanks, ybic >>>> nic... :) >>>> >>>> ______________________________**_________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> > >>>> >>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> >>>> >>>> >>>> ______________________________**_________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Thu Jan 3 12:20:20 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Thu, 03 Jan 2013 19:20:20 +0000 Subject: [sword-devel] =?utf-8?q?ISV_status=3F?= Message-ID: Andrew, this is now quite enough. Please desist posting further onto our list. Your presence is undesired Sent from my HTC ----- Reply message ----- From: "Andrew Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Thu, Jan 3, 2013 18:53 Done. I made it available here only in response to this request .. ~A On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: Andrew, this document is copyrighted. We do not have permission to distribute it. You certainly and absolutely do not have permission to distribute it, much less to distribute it and claim that we have permission to distribute it. Remove it immediately. --Chris On 1/3/2013 9:37 AM, Andrew Thule wrote: I believe there's an OSIS file that contains both testaments ... I can forward it if it helps this effort. There are least two versification problems (I haven't bothered to address yet) INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content to 1Sam.10.27 INFO(V11N): Rev.13 is not in the KJV versification. Appending content to Rev.12.17 I've placed a mod based on this OSIS file in my repo if anyone interested: Repository: 1XO Host: ftp.1xo.net /1xo/pub/sword/betaraw ~A On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter > wrote: ? ? Hi Team :) ? ? I was wondering where we were at with updating the ISV to include ? ? both the OT & NT? ? ? There was some chatter here about a year ago about it, but it ? ? sounded yuck, given we needed to convert the text from a Word ? ? document... ?:/ ? ? Thanks, ybic ? ? ? ? ? ? ?nic... ?:) ? ? _______________________________________________ ? ? sword-devel mailing list: sword-devel at crosswire.org ? ? ? ? http://www.crosswire.org/mailman/listinfo/sword-devel ? ? Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 12:56:12 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 14:56:12 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: Come now Peter, don't be so quick to find fault. The Crosswire repository currently contains version 1.5 of the ISV module. Nic's question was asking about the inclusion of the OT in that module. The Crosswire site doesn't say anything about the status of this module, and Nic's question seems to suggest he was not aware Crosswire was prohibited from distributed a later versions of this module. His comment was specifically asking about the ISV with OT included suggesting this was already direction that was being pursued. I was trying to extend an offer to help (as a volunteer). I certainly wasn't aware that permission hadn't been obtained to distribute the ISV with the OT, and the fact the ISV is already distributed with the NT suggests (perhaps incorrectly) that permission has been already obtained. Once Chris made it known that Crosswire has no such permission to distribute newer versions of the ISV I did exactly as Chris asked. So what infraction have I committed now? Respectfully, if every time a newcomer or volunteer's offer is met with criticism or controversy the treatment of newcomers and volunteers in this group is going to appear somewhat suspect and unwelcoming. It's a very good way to drive people away from a project. If my lack of awareness of this prohibition on the ISV is why you're asking me to leave - that says much about this community. Now that I know Crosswire doesn't have permission to distribute versions of the ISV other than the one currently in the repository, I'll respect that. If others feel as you do, that outside contributions are unwelcome here - I will kick the sand from my sandals and leave ~A On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: > Andrew, this is now quite enough. Please desist posting further onto our > list. Your presence is undesired > > Sent from my HTC > > > ----- Reply message ----- > From: "Andrew Thule" > To: "SWORD Developers' Collaboration Forum" > Subject: [sword-devel] ISV status? > Date: Thu, Jan 3, 2013 18:53 > > > Done. > > I made it available here only in response to this request .. > > ~A > > > On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: > >> Andrew, this document is copyrighted. We do not have permission to >> distribute it. You certainly and absolutely do not have permission to >> distribute it, much less to distribute it and claim that we have permission >> to distribute it. >> >> Remove it immediately. >> >> --Chris >> >> >> >> On 1/3/2013 9:37 AM, Andrew Thule wrote: >> >>> I believe there's an OSIS file that contains both testaments ... I can >>> forward it if it helps this effort. >>> >>> There are least two versification problems (I haven't bothered to >>> address yet) >>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >>> to 1Sam.10.27 >>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to >>> Rev.12.17 >>> >>> I've placed a mod based on this OSIS file in my repo if anyone >>> interested: >>> Repository: 1XO >>> Host: ftp.1xo.net >>> >>> /1xo/pub/sword/betaraw >>> >>> ~A >>> >>> >>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >> > wrote: >>> >>> >>> Hi Team :) >>> >>> I was wondering where we were at with updating the ISV to include >>> both the OT & NT? >>> There was some chatter here about a year ago about it, but it >>> sounded yuck, given we needed to convert the text from a Word >>> document... :/ >>> >>> Thanks, ybic >>> nic... :) >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> > >>> >>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 13:30:05 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 15:30:05 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: I should add that prior to doing anything I did check the isv.conf file which says this: DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire From dmsmith at crosswire.org Thu Jan 3 13:35:38 2013 From: dmsmith at crosswire.org (DM Smith) Date: Thu, 3 Jan 2013 15:35:38 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> I can see how you might conclude that. However, when we get permission for a copyrighted work, we get permission for that copyright. If the work is updated, there is a new copyright and we have to obtain permission for that. In Him, DM On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: > I should add that prior to doing anything I did check the isv.conf file which says this: > DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire > > > From .conf file at least, any reasonable person would conclude that permission had already been obtained to distribute (and redistribute) ISV and any additional revisions. > > ~A > > > On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: > Come now Peter, don't be so quick to find fault. > > The Crosswire repository currently contains version 1.5 of the ISV module. Nic's question was asking about the inclusion of the OT in that module. The Crosswire site doesn't say anything about the status of this module, and Nic's question seems to suggest he was not aware Crosswire was prohibited from distributed a later versions of this module. His comment was specifically asking about the ISV with OT included suggesting this was already direction that was being pursued. > > I was trying to extend an offer to help (as a volunteer). I certainly wasn't aware that permission hadn't been obtained to distribute the ISV with the OT, and the fact the ISV is already distributed with the NT suggests (perhaps incorrectly) that permission has been already obtained. Once Chris made it known that Crosswire has no such permission to distribute newer versions of the ISV I did exactly as Chris asked. So what infraction have I committed now? > > Respectfully, if every time a newcomer or volunteer's offer is met with criticism or controversy the treatment of newcomers and volunteers in this group is going to appear somewhat suspect and unwelcoming. It's a very good way to drive people away from a project. If my lack of awareness of this prohibition on the ISV is why you're asking me to leave - that says much about this community. > > Now that I know Crosswire doesn't have permission to distribute versions of the ISV other than the one currently in the repository, I'll respect that. If others feel as you do, that outside contributions are unwelcome here - I will kick the sand from my sandals and leave > > ~A > > On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: > Andrew, this is now quite enough. Please desist posting further onto our list. Your presence is undesired > > Sent from my HTC > > > ----- Reply message ----- > From: "Andrew Thule" > To: "SWORD Developers' Collaboration Forum" > Subject: [sword-devel] ISV status? > Date: Thu, Jan 3, 2013 18:53 > > > Done. > > I made it available here only in response to this request .. > > ~A > > > On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: > Andrew, this document is copyrighted. We do not have permission to distribute it. You certainly and absolutely do not have permission to distribute it, much less to distribute it and claim that we have permission to distribute it. > > Remove it immediately. > > --Chris > > > > On 1/3/2013 9:37 AM, Andrew Thule wrote: > I believe there's an OSIS file that contains both testaments ... I can > forward it if it helps this effort. > > There are least two versification problems (I haven't bothered to > address yet) > INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content > to 1Sam.10.27 > INFO(V11N): Rev.13 is not in the KJV versification. Appending content to > Rev.12.17 > > I've placed a mod based on this OSIS file in my repo if anyone interested: > Repository: 1XO > Host: ftp.1xo.net > > /1xo/pub/sword/betaraw > > ~A > > > On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter > wrote: > > > Hi Team :) > > I was wondering where we were at with updating the ISV to include > both the OT & NT? > There was some chatter here about a year ago about it, but it > sounded yuck, given we needed to convert the text from a Word > document... :/ > > Thanks, ybic > nic... :) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 13:39:15 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 15:39:15 -0500 Subject: [sword-devel] Beta modules question In-Reply-To: References: Message-ID: This site wasn't on my radar, but I find it very useful: http://crosswire.org/wiki/Modules_in_the_beta_repository#Commentary_Modules Many of these (well documented) issues appear easily fixed. For example the 'emptyvss' issues are likely simple problems to fix. It appears the purpose of this page is to impose a QA process on modules before they are permitted in the main. If so, there also appears to be procedural impediments easily solved (such as confirming a module appears complete ..etc) Does each module have a contact or point person in charge, or if someone is willing to work on some of these issues what's the procedure for offering to help fix some of these issues? ~A On Tue, Jan 1, 2013 at 10:27 PM, Nic Carter wrote: > > Heya all, > > Just a quick question about beta modules. > Currently we have the wiki page that is meant to be where we "report" > problems. I have been emailed again about the Barnes Notes module and > looking at the entry for it on the wiki at > http://crosswire.org/wiki/Modules_in_the_beta_repository#Commentary_Modulesshows that the reported issues I was emailed are already on that wiki page. > Looking at the conf file for the module doesn't let me know the source of > the text, and so there is nothing I can do to look into the problems > reported. > > My suggestion is that perhaps we should remove modules from the beta repo > that are not going to be updated? It has been 5 years since that module was > "updated" and these bugs in the module have been noted at several points on > the wiki since then, including in 2008, 2009 & 2012 (observed via a very > quick search of the history of that wiki page). > Alternatively, for this module a quick re-encoding as UTF-8 would fix the > most noticeable problem ;) > > Thanks heaps, ybic > nic... :) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 13:42:16 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 15:42:16 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: Thanks for the clarification DM. Perhaps for the sake of clarity then, the .conf file's "DistributionLicense=" attribute could contain the version for which permission was granted (rather than appearing to be generic). ~A On Thu, Jan 3, 2013 at 3:35 PM, DM Smith wrote: > I can see how you might conclude that. > > However, when we get permission for a copyrighted work, we get permission > for that copyright. If the work is updated, there is a new copyright and we > have to obtain permission for that. > > In Him, > DM > > > On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: > > I should add that prior to doing anything I did check the isv.conf file > which says this: > DistributionLicense=Copyrighted; Permission to distribute granted to > CrossWire > > > From .conf file at least, any reasonable person would conclude that > permission had already been obtained to distribute (and redistribute) ISV > and any additional revisions. > > ~A > > > On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: > >> Come now Peter, don't be so quick to find fault. >> >> The Crosswire repository currently contains version 1.5 of the ISV >> module. Nic's question was asking about the inclusion of the OT in that >> module. The Crosswire site doesn't say anything about the status of this >> module, and Nic's question seems to suggest he was not aware Crosswire was >> prohibited from distributed a later versions of this module. His comment >> was specifically asking about the ISV with OT included suggesting this was >> already direction that was being pursued. >> >> I was trying to extend an offer to help (as a volunteer). I certainly >> wasn't aware that permission hadn't been obtained to distribute the ISV >> with the OT, and the fact the ISV is already distributed with the NT >> suggests (perhaps incorrectly) that permission has been already obtained. >> Once Chris made it known that Crosswire has no such permission to >> distribute newer versions of the ISV I did exactly as Chris asked. So what >> infraction have I committed now? >> >> Respectfully, if every time a newcomer or volunteer's offer is met with >> criticism or controversy the treatment of newcomers and volunteers in this >> group is going to appear somewhat suspect and unwelcoming. It's a very >> good way to drive people away from a project. If my lack of awareness of >> this prohibition on the ISV is why you're asking me to leave - that says >> much about this community. >> >> Now that I know Crosswire doesn't have permission to distribute versions >> of the ISV other than the one currently in the repository, I'll respect >> that. If others feel as you do, that outside contributions are unwelcome >> here - I will kick the sand from my sandals and leave >> >> ~A >> >> On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: >> >>> Andrew, this is now quite enough. Please desist posting further onto our >>> list. Your presence is undesired >>> >>> Sent from my HTC >>> >>> >>> ----- Reply message ----- >>> From: "Andrew Thule" >>> To: "SWORD Developers' Collaboration Forum" >>> Subject: [sword-devel] ISV status? >>> Date: Thu, Jan 3, 2013 18:53 >>> >>> >>> Done. >>> >>> I made it available here only in response to this request .. >>> >>> ~A >>> >>> >>> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: >>> >>>> Andrew, this document is copyrighted. We do not have permission to >>>> distribute it. You certainly and absolutely do not have permission to >>>> distribute it, much less to distribute it and claim that we have permission >>>> to distribute it. >>>> >>>> Remove it immediately. >>>> >>>> --Chris >>>> >>>> >>>> >>>> On 1/3/2013 9:37 AM, Andrew Thule wrote: >>>> >>>>> I believe there's an OSIS file that contains both testaments ... I can >>>>> forward it if it helps this effort. >>>>> >>>>> There are least two versification problems (I haven't bothered to >>>>> address yet) >>>>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >>>>> to 1Sam.10.27 >>>>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content >>>>> to >>>>> Rev.12.17 >>>>> >>>>> I've placed a mod based on this OSIS file in my repo if anyone >>>>> interested: >>>>> Repository: 1XO >>>>> Host: ftp.1xo.net >>>>> >>>>> /1xo/pub/sword/betaraw >>>>> >>>>> ~A >>>>> >>>>> >>>>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >>>> > wrote: >>>>> >>>>> >>>>> Hi Team :) >>>>> >>>>> I was wondering where we were at with updating the ISV to include >>>>> both the OT & NT? >>>>> There was some chatter here about a year ago about it, but it >>>>> sounded yuck, given we needed to convert the text from a Word >>>>> document... :/ >>>>> >>>>> Thanks, ybic >>>>> nic... :) >>>>> >>>>> ______________________________**_________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> > >>>>> >>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>>> >>>>> >>>>> >>>>> ______________________________**_________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>>> >>>> >>>> ______________________________**_________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 13:44:52 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 15:44:52 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: I just thought about this a bit more .. I suppose that's what "Version=1.5" is for ... Nevermind. ~A On Thu, Jan 3, 2013 at 3:42 PM, Andrew Thule wrote: > Thanks for the clarification DM. > Perhaps for the sake of clarity then, the .conf file's > "DistributionLicense=" attribute could contain the version for which > permission was granted (rather than appearing to be generic). > > ~A > > > On Thu, Jan 3, 2013 at 3:35 PM, DM Smith wrote: > >> I can see how you might conclude that. >> >> However, when we get permission for a copyrighted work, we get permission >> for that copyright. If the work is updated, there is a new copyright and we >> have to obtain permission for that. >> >> In Him, >> DM >> >> >> On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: >> >> I should add that prior to doing anything I did check the isv.conf file >> which says this: >> DistributionLicense=Copyrighted; Permission to distribute granted to >> CrossWire >> >> >> From .conf file at least, any reasonable person would conclude that >> permission had already been obtained to distribute (and redistribute) ISV >> and any additional revisions. >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: >> >>> Come now Peter, don't be so quick to find fault. >>> >>> The Crosswire repository currently contains version 1.5 of the ISV >>> module. Nic's question was asking about the inclusion of the OT in that >>> module. The Crosswire site doesn't say anything about the status of this >>> module, and Nic's question seems to suggest he was not aware Crosswire was >>> prohibited from distributed a later versions of this module. His comment >>> was specifically asking about the ISV with OT included suggesting this was >>> already direction that was being pursued. >>> >>> I was trying to extend an offer to help (as a volunteer). I certainly >>> wasn't aware that permission hadn't been obtained to distribute the ISV >>> with the OT, and the fact the ISV is already distributed with the NT >>> suggests (perhaps incorrectly) that permission has been already obtained. >>> Once Chris made it known that Crosswire has no such permission to >>> distribute newer versions of the ISV I did exactly as Chris asked. So what >>> infraction have I committed now? >>> >>> Respectfully, if every time a newcomer or volunteer's offer is met with >>> criticism or controversy the treatment of newcomers and volunteers in this >>> group is going to appear somewhat suspect and unwelcoming. It's a very >>> good way to drive people away from a project. If my lack of awareness of >>> this prohibition on the ISV is why you're asking me to leave - that says >>> much about this community. >>> >>> Now that I know Crosswire doesn't have permission to distribute versions >>> of the ISV other than the one currently in the repository, I'll respect >>> that. If others feel as you do, that outside contributions are unwelcome >>> here - I will kick the sand from my sandals and leave >>> >>> ~A >>> >>> On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: >>> >>>> Andrew, this is now quite enough. Please desist posting further onto >>>> our list. Your presence is undesired >>>> >>>> Sent from my HTC >>>> >>>> >>>> ----- Reply message ----- >>>> From: "Andrew Thule" >>>> To: "SWORD Developers' Collaboration Forum" >>>> Subject: [sword-devel] ISV status? >>>> Date: Thu, Jan 3, 2013 18:53 >>>> >>>> >>>> Done. >>>> >>>> I made it available here only in response to this request .. >>>> >>>> ~A >>>> >>>> >>>> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: >>>> >>>>> Andrew, this document is copyrighted. We do not have permission to >>>>> distribute it. You certainly and absolutely do not have permission to >>>>> distribute it, much less to distribute it and claim that we have permission >>>>> to distribute it. >>>>> >>>>> Remove it immediately. >>>>> >>>>> --Chris >>>>> >>>>> >>>>> >>>>> On 1/3/2013 9:37 AM, Andrew Thule wrote: >>>>> >>>>>> I believe there's an OSIS file that contains both testaments ... I can >>>>>> forward it if it helps this effort. >>>>>> >>>>>> There are least two versification problems (I haven't bothered to >>>>>> address yet) >>>>>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >>>>>> to 1Sam.10.27 >>>>>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content >>>>>> to >>>>>> Rev.12.17 >>>>>> >>>>>> I've placed a mod based on this OSIS file in my repo if anyone >>>>>> interested: >>>>>> Repository: 1XO >>>>>> Host: ftp.1xo.net >>>>>> >>>>>> /1xo/pub/sword/betaraw >>>>>> >>>>>> ~A >>>>>> >>>>>> >>>>>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >>>>> > wrote: >>>>>> >>>>>> >>>>>> Hi Team :) >>>>>> >>>>>> I was wondering where we were at with updating the ISV to include >>>>>> both the OT & NT? >>>>>> There was some chatter here about a year ago about it, but it >>>>>> sounded yuck, given we needed to convert the text from a Word >>>>>> document... :/ >>>>>> >>>>>> Thanks, ybic >>>>>> nic... :) >>>>>> >>>>>> ______________________________**_________________ >>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>> > >>>>>> >>>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>>> Instructions to unsubscribe/change your settings at above page >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ______________________________**_________________ >>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>>> Instructions to unsubscribe/change your settings at above page >>>>>> >>>>>> >>>>> >>>>> ______________________________**_________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 3 13:46:33 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 15:46:33 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: If there are prohibitions against distributions of newer revisions of the text, this needs to be documented somewhere; for how else will volunteers know they are restricted to working with particular versions of text? ~A On Thu, Jan 3, 2013 at 3:44 PM, Andrew Thule wrote: > I just thought about this a bit more .. I suppose that's what > "Version=1.5" is for ... > > Nevermind. > ~A > > > On Thu, Jan 3, 2013 at 3:42 PM, Andrew Thule wrote: > >> Thanks for the clarification DM. >> Perhaps for the sake of clarity then, the .conf file's >> "DistributionLicense=" attribute could contain the version for which >> permission was granted (rather than appearing to be generic). >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 3:35 PM, DM Smith wrote: >> >>> I can see how you might conclude that. >>> >>> However, when we get permission for a copyrighted work, we get >>> permission for that copyright. If the work is updated, there is a new >>> copyright and we have to obtain permission for that. >>> >>> In Him, >>> DM >>> >>> >>> On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: >>> >>> I should add that prior to doing anything I did check the isv.conf file >>> which says this: >>> DistributionLicense=Copyrighted; Permission to distribute granted to >>> CrossWire >>> >>> >>> From .conf file at least, any reasonable person would conclude that >>> permission had already been obtained to distribute (and redistribute) ISV >>> and any additional revisions. >>> >>> ~A >>> >>> >>> On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: >>> >>>> Come now Peter, don't be so quick to find fault. >>>> >>>> The Crosswire repository currently contains version 1.5 of the ISV >>>> module. Nic's question was asking about the inclusion of the OT in that >>>> module. The Crosswire site doesn't say anything about the status of this >>>> module, and Nic's question seems to suggest he was not aware Crosswire was >>>> prohibited from distributed a later versions of this module. His comment >>>> was specifically asking about the ISV with OT included suggesting this was >>>> already direction that was being pursued. >>>> >>>> I was trying to extend an offer to help (as a volunteer). I certainly >>>> wasn't aware that permission hadn't been obtained to distribute the ISV >>>> with the OT, and the fact the ISV is already distributed with the NT >>>> suggests (perhaps incorrectly) that permission has been already obtained. >>>> Once Chris made it known that Crosswire has no such permission to >>>> distribute newer versions of the ISV I did exactly as Chris asked. So what >>>> infraction have I committed now? >>>> >>>> Respectfully, if every time a newcomer or volunteer's offer is met with >>>> criticism or controversy the treatment of newcomers and volunteers in this >>>> group is going to appear somewhat suspect and unwelcoming. It's a very >>>> good way to drive people away from a project. If my lack of awareness of >>>> this prohibition on the ISV is why you're asking me to leave - that says >>>> much about this community. >>>> >>>> Now that I know Crosswire doesn't have permission to distribute >>>> versions of the ISV other than the one currently in the repository, I'll >>>> respect that. If others feel as you do, that outside contributions are >>>> unwelcome here - I will kick the sand from my sandals and leave >>>> >>>> ~A >>>> >>>> On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: >>>> >>>>> Andrew, this is now quite enough. Please desist posting further onto >>>>> our list. Your presence is undesired >>>>> >>>>> Sent from my HTC >>>>> >>>>> >>>>> ----- Reply message ----- >>>>> From: "Andrew Thule" >>>>> To: "SWORD Developers' Collaboration Forum" >>>> > >>>>> Subject: [sword-devel] ISV status? >>>>> Date: Thu, Jan 3, 2013 18:53 >>>>> >>>>> >>>>> Done. >>>>> >>>>> I made it available here only in response to this request .. >>>>> >>>>> ~A >>>>> >>>>> >>>>> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: >>>>> >>>>>> Andrew, this document is copyrighted. We do not have permission to >>>>>> distribute it. You certainly and absolutely do not have permission to >>>>>> distribute it, much less to distribute it and claim that we have permission >>>>>> to distribute it. >>>>>> >>>>>> Remove it immediately. >>>>>> >>>>>> --Chris >>>>>> >>>>>> >>>>>> >>>>>> On 1/3/2013 9:37 AM, Andrew Thule wrote: >>>>>> >>>>>>> I believe there's an OSIS file that contains both testaments ... I >>>>>>> can >>>>>>> forward it if it helps this effort. >>>>>>> >>>>>>> There are least two versification problems (I haven't bothered to >>>>>>> address yet) >>>>>>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending >>>>>>> content >>>>>>> to 1Sam.10.27 >>>>>>> INFO(V11N): Rev.13 is not in the KJV versification. Appending >>>>>>> content to >>>>>>> Rev.12.17 >>>>>>> >>>>>>> I've placed a mod based on this OSIS file in my repo if anyone >>>>>>> interested: >>>>>>> Repository: 1XO >>>>>>> Host: ftp.1xo.net >>>>>>> >>>>>>> /1xo/pub/sword/betaraw >>>>>>> >>>>>>> ~A >>>>>>> >>>>>>> >>>>>>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >>>>>> > wrote: >>>>>>> >>>>>>> >>>>>>> Hi Team :) >>>>>>> >>>>>>> I was wondering where we were at with updating the ISV to include >>>>>>> both the OT & NT? >>>>>>> There was some chatter here about a year ago about it, but it >>>>>>> sounded yuck, given we needed to convert the text from a Word >>>>>>> document... :/ >>>>>>> >>>>>>> Thanks, ybic >>>>>>> nic... :) >>>>>>> >>>>>>> ______________________________**_________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> > >>>>>>> >>>>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above page >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ______________________________**_________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above page >>>>>>> >>>>>>> >>>>>> >>>>>> ______________________________**_________________ >>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>> http://www.crosswire.org/**mailman/listinfo/sword-devel >>>>>> Instructions to unsubscribe/change your settings at above page >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>> >>>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Thu Jan 3 13:53:54 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 3 Jan 2013 14:53:54 -0600 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: On Thu, Jan 3, 2013 at 2:44 PM, Andrew Thule wrote: > I just thought about this a bit more .. I suppose that's what "Version=1.5" > is for ... No, the Copyright limitation applies to the source material. It's very possible that multiple versions of the module could be made from the same initial source copy as bugs are uncovered in the encoding, in the transformation process, in the conf file, etc. So the Copyright permission is not given for Version 1.5 of the module but for a particular copy of the original material received from the Copyright holder. There is no way to know from most conf files if there has been only one or possibly dozens of versions of the source material iterated through. In this case it is likely that there are no more than 5 copies of the source text but more likely there was only 1 or 2 versions received from upstream and the other revisions represent bug fixes in the importation or distribution process. --Greg > > Nevermind. > ~A > > > On Thu, Jan 3, 2013 at 3:42 PM, Andrew Thule wrote: >> >> Thanks for the clarification DM. >> Perhaps for the sake of clarity then, the .conf file's >> "DistributionLicense=" attribute could contain the version for which >> permission was granted (rather than appearing to be generic). >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 3:35 PM, DM Smith wrote: >>> >>> I can see how you might conclude that. >>> >>> However, when we get permission for a copyrighted work, we get permission >>> for that copyright. If the work is updated, there is a new copyright and we >>> have to obtain permission for that. >>> >>> In Him, >>> DM >>> >>> >>> On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: >>> >>> I should add that prior to doing anything I did check the isv.conf file >>> which says this: >>> DistributionLicense=Copyrighted; Permission to distribute granted to >>> CrossWire >>> >>> >>> From .conf file at least, any reasonable person would conclude that >>> permission had already been obtained to distribute (and redistribute) ISV >>> and any additional revisions. >>> >>> ~A >>> >>> >>> On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: >>>> >>>> Come now Peter, don't be so quick to find fault. >>>> >>>> The Crosswire repository currently contains version 1.5 of the ISV >>>> module. Nic's question was asking about the inclusion of the OT in that >>>> module. The Crosswire site doesn't say anything about the status of this >>>> module, and Nic's question seems to suggest he was not aware Crosswire was >>>> prohibited from distributed a later versions of this module. His comment >>>> was specifically asking about the ISV with OT included suggesting this was >>>> already direction that was being pursued. >>>> >>>> I was trying to extend an offer to help (as a volunteer). I certainly >>>> wasn't aware that permission hadn't been obtained to distribute the ISV with >>>> the OT, and the fact the ISV is already distributed with the NT suggests >>>> (perhaps incorrectly) that permission has been already obtained. Once Chris >>>> made it known that Crosswire has no such permission to distribute newer >>>> versions of the ISV I did exactly as Chris asked. So what infraction have I >>>> committed now? >>>> >>>> Respectfully, if every time a newcomer or volunteer's offer is met with >>>> criticism or controversy the treatment of newcomers and volunteers in this >>>> group is going to appear somewhat suspect and unwelcoming. It's a very good >>>> way to drive people away from a project. If my lack of awareness of this >>>> prohibition on the ISV is why you're asking me to leave - that says much >>>> about this community. >>>> >>>> Now that I know Crosswire doesn't have permission to distribute versions >>>> of the ISV other than the one currently in the repository, I'll respect >>>> that. If others feel as you do, that outside contributions are unwelcome >>>> here - I will kick the sand from my sandals and leave >>>> >>>> ~A >>>> >>>> On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: >>>>> >>>>> Andrew, this is now quite enough. Please desist posting further onto >>>>> our list. Your presence is undesired >>>>> >>>>> Sent from my HTC >>>>> >>>>> >>>>> ----- Reply message ----- >>>>> From: "Andrew Thule" >>>>> To: "SWORD Developers' Collaboration Forum" >>>>> Subject: [sword-devel] ISV status? >>>>> Date: Thu, Jan 3, 2013 18:53 >>>>> >>>>> >>>>> Done. >>>>> >>>>> I made it available here only in response to this request .. >>>>> >>>>> ~A >>>>> >>>>> >>>>> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little >>>>> wrote: >>>>>> >>>>>> Andrew, this document is copyrighted. We do not have permission to >>>>>> distribute it. You certainly and absolutely do not have permission to >>>>>> distribute it, much less to distribute it and claim that we have permission >>>>>> to distribute it. >>>>>> >>>>>> Remove it immediately. >>>>>> >>>>>> --Chris >>>>>> >>>>>> >>>>>> >>>>>> On 1/3/2013 9:37 AM, Andrew Thule wrote: >>>>>>> >>>>>>> I believe there's an OSIS file that contains both testaments ... I >>>>>>> can >>>>>>> forward it if it helps this effort. >>>>>>> >>>>>>> There are least two versification problems (I haven't bothered to >>>>>>> address yet) >>>>>>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending >>>>>>> content >>>>>>> to 1Sam.10.27 >>>>>>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content >>>>>>> to >>>>>>> Rev.12.17 >>>>>>> >>>>>>> I've placed a mod based on this OSIS file in my repo if anyone >>>>>>> interested: >>>>>>> Repository: 1XO >>>>>>> Host: ftp.1xo.net >>>>>>> >>>>>>> /1xo/pub/sword/betaraw >>>>>>> >>>>>>> ~A >>>>>>> >>>>>>> >>>>>>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter >>>>>> > wrote: >>>>>>> >>>>>>> >>>>>>> Hi Team :) >>>>>>> >>>>>>> I was wondering where we were at with updating the ISV to include >>>>>>> both the OT & NT? >>>>>>> There was some chatter here about a year ago about it, but it >>>>>>> sounded yuck, given we needed to convert the text from a Word >>>>>>> document... :/ >>>>>>> >>>>>>> Thanks, ybic >>>>>>> nic... :) >>>>>>> >>>>>>> _______________________________________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> >>>>>>> >>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above page >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above page >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dmsmith at crosswire.org Thu Jan 3 13:54:52 2013 From: dmsmith at crosswire.org (DM Smith) Date: Thu, 3 Jan 2013 15:54:52 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: <8A782373-50B8-4706-A51A-38121B2705AF@crosswire.org> By and large, we use the upstream source for a text without modifying it at all. If we find errors or problems, we feed them back upstream. This benefits everyone, not just us. When a source is not copyrighted, we look for the best source we can find. When it is copyrighted we get it from the publisher in the form that they are willing to provide. If we have an error that is due to our import process, we'll fix that and rebuild the module. The only text that we maintain is the KJV. I am the pumpkin holder for that. I get downstream notifications every now and them and am grateful for that. In Him, DM On Jan 3, 2013, at 3:46 PM, Andrew Thule wrote: > If there are prohibitions against distributions of newer revisions of the text, this needs to be documented somewhere; for how else will volunteers know they are restricted to working with particular versions of text? > > ~A > > > On Thu, Jan 3, 2013 at 3:44 PM, Andrew Thule wrote: > I just thought about this a bit more .. I suppose that's what "Version=1.5" is for ... > > Nevermind. > ~A > > > On Thu, Jan 3, 2013 at 3:42 PM, Andrew Thule wrote: > Thanks for the clarification DM. > Perhaps for the sake of clarity then, the .conf file's "DistributionLicense=" attribute could contain the version for which permission was granted (rather than appearing to be generic). > > ~A > > > On Thu, Jan 3, 2013 at 3:35 PM, DM Smith wrote: > I can see how you might conclude that. > > However, when we get permission for a copyrighted work, we get permission for that copyright. If the work is updated, there is a new copyright and we have to obtain permission for that. > > In Him, > DM > > > On Jan 3, 2013, at 3:30 PM, Andrew Thule wrote: > >> I should add that prior to doing anything I did check the isv.conf file which says this: >> DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire >> >> >> From .conf file at least, any reasonable person would conclude that permission had already been obtained to distribute (and redistribute) ISV and any additional revisions. >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule wrote: >> Come now Peter, don't be so quick to find fault. >> >> The Crosswire repository currently contains version 1.5 of the ISV module. Nic's question was asking about the inclusion of the OT in that module. The Crosswire site doesn't say anything about the status of this module, and Nic's question seems to suggest he was not aware Crosswire was prohibited from distributed a later versions of this module. His comment was specifically asking about the ISV with OT included suggesting this was already direction that was being pursued. >> >> I was trying to extend an offer to help (as a volunteer). I certainly wasn't aware that permission hadn't been obtained to distribute the ISV with the OT, and the fact the ISV is already distributed with the NT suggests (perhaps incorrectly) that permission has been already obtained. Once Chris made it known that Crosswire has no such permission to distribute newer versions of the ISV I did exactly as Chris asked. So what infraction have I committed now? >> >> Respectfully, if every time a newcomer or volunteer's offer is met with criticism or controversy the treatment of newcomers and volunteers in this group is going to appear somewhat suspect and unwelcoming. It's a very good way to drive people away from a project. If my lack of awareness of this prohibition on the ISV is why you're asking me to leave - that says much about this community. >> >> Now that I know Crosswire doesn't have permission to distribute versions of the ISV other than the one currently in the repository, I'll respect that. If others feel as you do, that outside contributions are unwelcome here - I will kick the sand from my sandals and leave >> >> ~A >> >> On Thu, Jan 3, 2013 at 2:20 PM, refdoc at gmx.net wrote: >> Andrew, this is now quite enough. Please desist posting further onto our list. Your presence is undesired >> >> Sent from my HTC >> >> >> ----- Reply message ----- >> From: "Andrew Thule" >> To: "SWORD Developers' Collaboration Forum" >> Subject: [sword-devel] ISV status? >> Date: Thu, Jan 3, 2013 18:53 >> >> >> Done. >> >> I made it available here only in response to this request .. >> >> ~A >> >> >> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little wrote: >> Andrew, this document is copyrighted. We do not have permission to distribute it. You certainly and absolutely do not have permission to distribute it, much less to distribute it and claim that we have permission to distribute it. >> >> Remove it immediately. >> >> --Chris >> >> >> >> On 1/3/2013 9:37 AM, Andrew Thule wrote: >> I believe there's an OSIS file that contains both testaments ... I can >> forward it if it helps this effort. >> >> There are least two versification problems (I haven't bothered to >> address yet) >> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content >> to 1Sam.10.27 >> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to >> Rev.12.17 >> >> I've placed a mod based on this OSIS file in my repo if anyone interested: >> Repository: 1XO >> Host: ftp.1xo.net >> >> /1xo/pub/sword/betaraw >> >> ~A >> >> >> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter > > wrote: >> >> >> Hi Team :) >> >> I was wondering where we were at with updating the ISV to include >> both the OT & NT? >> There was some chatter here about a year ago about it, but it >> sounded yuck, given we needed to convert the text from a Word >> document... :/ >> >> Thanks, ybic >> nic... :) >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> >> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaak at ristioja.ee Thu Jan 3 14:11:28 2013 From: jaak at ristioja.ee (Jaak Ristioja) Date: Thu, 03 Jan 2013 23:11:28 +0200 Subject: [sword-devel] Patches to fix compiler warnings In-Reply-To: References: <50D3A00E.8060909@ristioja.ee> Message-ID: <50E5F400.9020700@ristioja.ee> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02.01.2013 09:22, Nic Carter wrote: > Thanks for these. > > Hopefully some kind soul will apply them? When I first posted the patches I thought I'll wait until 2013 before taking any further steps. But it has been a very busy time for me and possibly also for the Sword developers, so I think I'll wait a little more until I have more time to work on Sword (maybe some time next week). > For those who are interested, some fun articles related to this > stuff: > > * > http://inessential.com/2012/12/31/coders_in_the_hands_of_an_angry_god > > * http://boredzo.org/blog/archives/2009-11-07/warnings > * (more appropriate to Obj-C) > http://ashfurrow.com/blog/seven-deadly-sins-of-modern-objective-c I can't fully agree with the "treat all warnings as errors" approach, since as far as I know there are some warnings which are very difficult to work around, e.g. warnings about "#pragma STDC FENV_ACCESS ON" not being supported by certain compilers or Clang warnings about struct/class padding. Some warnings can be annotated with comments (which might also show up in the warnings) so that developers wouldn't try to fix what can't be fixed in a straightforward manner. In my opinion short variable names are also fine if they are either simple temporary variables, if their declarations are well documented or if their semantics are obvious just by looking at their type. Of course longer and more descriptive names are recommended, but in case stuff doesn't fit well horizontally I've usually abbreviated them, especially if their scope is limited. The biggest issue with short variable names is that they sometimes (and not very rarely) make code difficult to read and understand. Blessings, Jaak -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQgcBAEBAgAGBQJQ5fP8AAoJEEqsYmEt1rCOAedAAK/zdbAYoBA5aIBq2CtlbCRl o70jF0ORE1u/aVMtZ9tsfipbknYKupVOYWEwBJ8ZpO20fSUag4NYrmySThD4LvY9 1sVex6LEckT9lsMVEnNNOGw6b5nJ0JyPIuCYG1cxsFg/pprsgFY26eZZiIHNj1zQ 6/KVgkjG95QNncPRcY4hAjvAOgYru84AQroz0Cy5K/GJBMxitDVfoTLH9+dmLt7T +0Ovg8X+/1vnO11PYxtHLXSL05kN1Ct4ETU86Os0A9MvrzUcgVkVzsT9qiAMmrvN 3dBF76ei8TU2DsST1LjlBCGK/stBA6aG78s/ERiOrcu6km3c0+11xtHOGPBjtv5p 1PibEz7UjzIPn1JAnCvIPReD0WhsWXpGnBEcLoQID1s5TDwCymtZoD2xXK11zu7B LpPv8Lxw4+1KjQtM4UekdsZJhIVHBqaXuW2JY9UY2MW9sgWPBNzymK8Owu6QIZNq Dg112utAAwK+zeQxZNPH0SsE3qmXoTWWAO7QFfLaxh26sVYcGQvIPoPyqsS3gr+g TCJ58JfIgpAlZnRedhJvBiEhmo4ijSwtewbzA7kHxeVeUxltqe+JX/wjjWJ9FE0V pzsw55niPHNSO5Y3USs6hnA1eQ/hL8kZ/z0WW8+Wwe8gEKt2rzLDm5ya1sJQDM2/ EFPWjI3poss3bLxxrHhkhjOMrJJ8VC56+8NDV9dkOJ+xUH+pLU/2N8u++JOxcLJU NBGcJSrBGwJB1CCI24U3mqszXSQLS/RG1QndiukYLY+nhZ5+mIIVo5Qo2H6RmDwz Nhtd8Xf0DU101Gu8mXzfzzShr9KHRPDZl1Pm9VR4B7jdKpJW6AIthRJdqfyj7b/u TnbGCJcDxC3YyckNRGUR+hiQV288YE4K+UhjdBPzo8RuFs1JZI1712lwiavUxdZQ OS/c+LM0brp4iGGDfZW1SDCJ7kQe8JQFT71Pwasyy7hTrpJx6Bfh8wzufWA9nFHI dkTHhkU4SomS0MZHhV8PKSjB0Pg6s4VTDjIIliJld5ViT88nZtVesBkl6XS2E8Qo snrQ6e7AeH4y4tG+9WIyW5D4L1xz4c6yz/xiGjVt8WJIQ0c9SwL3okyWcySUx1ax 9Lmjer9zQ01trIe6yJS17DChnxXsytOfJB5CD0i26gF+RDFTCf2w5lh5gCVZEgrf /kgax4310SzfQzM3DdLr66watwtP4ND8X4dyZ/xu9IMKXzOgJQ5oka63ocEmN8A1 1W/MS8hiSXGcESo61x9ok80mx/ArIYqyRE0i40PAH16x1kkDWMemdARhEluewsD7 24E5tCcVbfx08CRdI25hLnALkKqk4E8tXRxLPni7G1tzszjUO4TpL7FKIVQOrZuV L6knhLMe2kzuNivWGp9K7Hc3CIMqS0frlLxdIJocesVLi9PQir5oy3PM5K17KDoL jtc5iozF64JDV/158WnnaKJGEaFQI1A7rYMzxXk7RhRnPxFXdHVu0YRpC5kI26Qk vTP+e8Ic2Nxz/kbN3HLekyoNWbNdJZG9u2CUvJVo0dJrJasb1bjpq7EGjQXy/KKX GtpSEP/ihM55Y05zaC8qHXWZ9O4b3Juw05glmOvgjilLKKTHxbfg0EHceFG9JZaS R2BEVxJ0wDOBbEs26LmwzlxTB8cB9N5bp2qK1WjBt760JIEfrgHzI5IMAmLWvm/F HyjXTY8GjWITP3rSUnDwcqT5xK2ksw2dV5Oyb6XKwTWBQTFMV9NPHg2CG7HIo+P+ 9PiqYBdv6sfCNJ+MdOOP2Fom/Bv7nH6eu31baejP7uLf2c+lzx+zuzcfQxfCldYJ BCXNFp0sH2x9OLxday1wySC+k8OMxtrjwc0vdargwrsTLjJ2iaeMtRgEnCSXpNyy hESErc7gTlm1w+fxSd8APiy41scDK1d1ElfjBAFHRC3EjyKezsoOock/AaOiaRSP fpCqmzE++RBq5a4gUvKVAd3ybXwc6jI39m+1oqG6ODuB0H7Hxx+9K3jBkR5F2mxo POaYEc9jkXvRtlhYOi3O87I3aZvoHOUU4h6i79xSwVq4P+VRpeqQCTxOmZJSx1kU GhsnMUPd/SRS/7dZhoFt6fcXN3J/+EUGD0ytLH1wjHk0uKUXOYzhlRanJZUBDlyz raN1yfCbmbu3s9+II33xcj/ywYm0rqSFom1TzgY3rApBfsLvOZdPfr7rbcX94AT4 /HxB2MD42FBSwo0GFR0cKjxD3uaCnGLXHKBFVxRcQ13bXs5MY07b0qrTFblZo3QR lQHlSeMRpHZfUd7TB6psvXSDsg/3lCj4H7uJGPzBhhwVsTjJts8TBuiSxFpFLvEE ZDEEqO0wRpe9SiYHYMm6q/6zaMqZEIES0QIdLnnQuCwl3iZ9c6Muk1BAFtHnIDjS cr3MFkiOhOz47RITEshyEZCw8dt9I83UPpo3BR/mXJW7zJwS+O0cucUMYFcuDCH+ j9ljnUudjMHlfBwfTk35q9Xkx5jWmuT83NbEuurSOKRLbVei1WhBrOhEUc3YmWeu Yu1QlwmwW6LwWB7WB0um2VDQzkpjgHcqejlqh+R8VXB8snG/dU2E5ebcfYBFYEZt o/pP26nciWCn0sJ+q+Kqm15QL+JEiTSa3g0+WAGP4U51GZ891v3M1N+g2eMiLXj1 i/DVWNAvUZKVxURZlCnlJMjabwQfy5cN+QV4SRYEuaWRt4b/zRMzgGXa0Xc1CAeu XMOFJojyEPKtsOU1qgyj =IkPu -----END PGP SIGNATURE----- From refdoc at gmx.net Thu Jan 3 16:36:29 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Thu, 03 Jan 2013 23:36:29 +0000 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> Message-ID: <50E615FD.2080707@gmx.net> On 03/01/13 20:46, Andrew Thule wrote: > If there are prohibitions against distributions of newer revisions of > the text, this needs to be documented somewhere; for how else will > volunteers know they are restricted to working with particular versions > of text? You are no CrossWire volunteer. Peter From refdoc at gmx.net Thu Jan 3 16:40:37 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Thu, 03 Jan 2013 23:40:37 +0000 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: <50E616F5.3080009@gmx.net> On 03/01/13 19:56, Andrew Thule wrote: > If others feel as you do, that outside contributions are > unwelcome here - I will kick the sand from my sandals and leave I will correct that... On 03/01/13 1956 Andrew Thule should have written: > If others feel as you do, that my contributions are > unwelcome here - I will kick the sand from my sandals and leave From thulester at gmail.com Thu Jan 3 16:51:36 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 18:51:36 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <50E615FD.2080707@gmx.net> References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> <50E615FD.2080707@gmx.net> Message-ID: Peter, Have you read [James 2:13]? It's not clear why the hostility, but I'm trying to contribute here (albeit with lots of resistance). If there's some secret handshake, application form, or process other than signing up on this list that helps transition folks from being outsiders to being insiders, please point it out. Otherwise, close off the list to invite only, and advertise it as a secret cabal. Otherwise, your interpersonal efforts are better spent making people welcomed, rather than wrath and judgement. If I've done something wrong, please identify my short-comings so I may repent and learn. ~A On Thursday, January 3, 2013, Peter von Kaehne wrote: > On 03/01/13 20:46, Andrew Thule wrote: > >> If there are prohibitions against distributions of newer revisions of >> the text, this needs to be documented somewhere; for how else will >> volunteers know they are restricted to working with particular versions >> of text? >> > > You are no CrossWire volunteer. > > Peter > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niccarter at mac.com Thu Jan 3 17:25:56 2013 From: niccarter at mac.com (Nic Carter) Date: Fri, 04 Jan 2013 11:25:56 +1100 Subject: [sword-devel] Beta modules question In-Reply-To: <50E581F2.3070209@crosswire.org> References: <50E5330A.9060905@crosswire.org> <9B4337E8-D000-424A-BDBE-0104E7F1EA87@mac.com> <50E581F2.3070209@crosswire.org> Message-ID: <7024395B-8999-46DF-98E8-72DD55529F01@mac.com> On 04/01/2013, at 12:04 AM, Chris Little wrote: > The only repository not for general public use is not listed in masterRepoList.conf, and that's the experimental repository. > > The attic repositories are definitely intended for the public to use. If users care to, they can downgrade from a broken module (for example) from the attic repositories. Thanks for the replies, it seems I need to rethink how I present modules for download to users. I'll take on the advice given by you guys & see what I can do... :) Thanks, ybic nic... :) From refdoc at gmx.net Thu Jan 3 17:36:32 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Fri, 04 Jan 2013 00:36:32 +0000 Subject: [sword-devel] ISV status? In-Reply-To: References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> <50E615FD.2080707@gmx.net> Message-ID: <1357259792.2589.22.camel@peter-ThinkPad-X200s> On Thu, 2013-01-03 at 18:51 -0500, Andrew Thule wrote: > Have you read [James 2:13]? It's not clear why the hostility, but I'm > trying to contribute here (albeit with lots of resistance). Resistance comes about when someone with a severe case of stubbornness ignores being told that a particular "contribution" is not desired, not asked for nor even legal. Cases in point - your mirrors, Qumran translations and now this here. Kindness did not work. Explanation did not work. Bluntness did not work. You still distribute the Qumran translations and at this point your further presence here is undesired. > If there's some secret handshake, application form, or process other > than signing up on this list that helps transition folks from being > outsiders to being insiders, please point it out. Otherwise, close > off the list to invite only, and advertise it as a secret cabal. The process is to subscribe to mailing list, maybe ask what needs to get done, certainly get the agreement of others before one does things which might have an impact on the project, listen to when objections are raised and learn when mistakes are pointed out. You did the first thing. None of the rest. > Otherwise, your interpersonal efforts are better spent making people > welcomed, rather than wrath and judgement. > There is no wrath or judgement, but simple, yet utter exasperation that someone seemingly intelligent enough to use a computer is unable to learn that a) copyright is important to us b) advertising breaches of copyright on this mailing list is verboten c) maintaining good relationships with publishers is a priority to us. > If I've done something wrong, please identify my short-comings so I > may repent and learn. Again? Please read this email from start. Peter -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From thulester at gmail.com Thu Jan 3 18:49:54 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 3 Jan 2013 20:49:54 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <1357259792.2589.22.camel@peter-ThinkPad-X200s> References: <682E103C-4FB4-406F-8DB9-13AAF652F772@crosswire.org> <50E615FD.2080707@gmx.net> <1357259792.2589.22.camel@peter-ThinkPad-X200s> Message-ID: On Thursday, January 3, 2013, Peter von Kaehne wrote: > On Thu, 2013-01-03 at 18:51 -0500, Andrew Thule wrote: > > Resistance comes about when someone with a severe case of stubbornness > ignores being told that a particular "contribution" is not desired, not > asked for nor even legal. Cases in point - your mirrors, Qumran > translations and now this here. Kindness did not work. Explanation did > not work. Bluntness did not work. You still distribute the Qumran > translations and at this point your further presence here is > undesired. > > Peter, that I construct modules apart from Crosswire should not be a source of conflict between us. As long as Crosswire is disinterested in the Qumran module, Crosswire has nought to say about it. That you do not exercise control over my repo shouldn't be a source of conflict either. Before I set a repo up I offered to subordinate it to Crosswire (which would have meant governed by policies of consensus). I also remember offering to generously host Crosswire mirrors at no cost to Crosswires (with the caveate they be perfect syncronisations, reflections). I seem to remember this generous offer being rebuffed soundly. I was not offended. It is not stubbornness on my part that I run a repo independent of your control, or create modules you have no interest in, given that in both cases I offered these efforts first to Crosswire, only to be met with hostility. If you're not interested - be disinterested! The process is to subscribe to mailing list, maybe ask what needs to get > done, certainly get the agreement of others before one does things which > might have an impact on the project, listen to when objections are > raised and learn when mistakes are pointed out. Clearly this is more than reasonable, and my actions show that with respect to Crosswire contributions I have complied and am willing to comply with every respect. You'll recall that when you could find no grounds to reject the Portuguese module that was constructed, and asked for the OSIS document you had no argument from me. This was only the second effort on my part you didn't criticize. What is not reasonable is the unspoken expectation that you exercise control over non-Crosswire modules, or repos you are free to ignore. On the one hand, the impression this list gives is that the long term goal is to decentralize repositories, yet in practice, this hasn't worked well because the one completely independent one that exists posses some kind of threat because it appears to fall outside your domain of control even though this didn't have to be the case. At some point you're going to have to decide if others can be trusted to contribute or not. a) copyright is important to us > b) advertising breaches of copyright on this mailing list is verboten > c) maintaining good relationships with publishers is a priority to us. > > No issues there. If I submit something for inclusion that is of questionable origin I fully expect a reprimand. However, at this point you apparently won't even let me contribute to discussion about a module you've already approved (ISV), therefore there are likely other issues that stand in the way (such as heavy handed, angry control issues). > If I've done something wrong, please identify my short-comings so I > > may repent and learn. > > Again? Please read this email from start. > > Sorry, I'll clarify: If I've done something wrong with respect to supporting the construction and distribution of Crosswire modules, please identify it so I can repent and learn. Since this post is actually about the ISV module, please let me know how my offer to help with this effort has not been in the spirit of cooperation. If your complaint is about my repo though, that is a separate issue. Feel free to provide advice on its management, but don't be offended if I continue to exercise independent judgement abouts its administration or chose to disregard it. (Please do reflect on how new-comers are treated when they offer their talents (especially given recent reflections about contributors having too little time)). Otherwise, with respect to contributing Crosswire modules, their construction, QA, and edits, I fully submit to your authority, and judgement. Your expectation I conform to your rule for this, is reasonable, and I'm willing to demonstrate this flexiblilty. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Thu Jan 3 23:35:47 2013 From: chrislit at crosswire.org (Chris Little) Date: Thu, 03 Jan 2013 22:35:47 -0800 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: <50E67843.7010308@crosswire.org> On 1/3/2013 12:30 PM, Andrew Thule wrote: > I should add that prior to doing anything I did check the isv.conf file > which says this: > DistributionLicense=Copyrighted; Permission to distribute granted to > CrossWire > > > From .conf file at least, any reasonable person would conclude that > permission had already been obtained to distribute (and redistribute) > ISV and any additional revisions. We've actually had specific discussions with you about our not wanting you to redistribute our modules, specifically because of copyrighted content such as this for which WE have permission. YOU are not CrossWire. Any reasonable person would conclude that he did not have permission to distribute unless his name were, by some coincidence, "CrossWire". I'm curious what your train of thought was that led you to conclude that YOU should distribute a module that we were not distributing, when your basis for distribution was a belief that WE had permission to distribute it. The .conf you had posted obviously was not for that version of the module, given that the SourceType was wrong and all of the other details simply reflected our released version: http://www.crosswire.org/ftpmirror/pub/sword/raw/mods.d/isv.conf The basis for the module you posted was outdated at the time it was produced and had been removed from the publisher's website by then. The OSIS document produced from this was furthermore not valid XML (unless it has been updated in the last year). So conversion from a Word document is still necessary. And unless the process for converting from that Word document can be replicated (via scripts) the whole exercise of producing that OSIS document was without value. --Chris From dmsmith at crosswire.org Fri Jan 4 07:09:51 2013 From: dmsmith at crosswire.org (DM Smith) Date: Fri, 4 Jan 2013 09:09:51 -0500 Subject: [sword-devel] CrossWire mirroring Message-ID: From time to time, interest has been expressed in mirroring CrossWire's SWORD modules. I thought I'd reiterate our policy. We strongly, very strongly, discourage mirroring of the SWORD module repository. Those modules for which CrossWire has obtained distribution permission from copyright holders must not be mirrored. These have "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire" in their conf. CrossWire maintains correspondence for each of these modules. Mirrors are seldom current/correct, despite intentions. On occasion we have unintentionally hosted modules for which we did not have permission. When presented with an ownership claim, we typically will take the module offline immediately and validate the claim. If the claim is false, we will put the module back up. If the claim is true, we obtain permission before putting the module back online or we don't put it back. This is an important part of our stewardship. If or when CrossWire has problems with distribution, we'll tackle the problem at that time. Probably with a "Content Delivery Network" of CrossWire owned servers. This or some variation of this probably should be in the wiki. In His Service, DM -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 4 13:11:41 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 4 Jan 2013 15:11:41 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <50E67843.7010308@crosswire.org> References: <50E67843.7010308@crosswire.org> Message-ID: On Fri, Jan 4, 2013 at 1:35 AM, Chris Little wrote: > We've actually had specific discussions with you about our not wanting you > to redistribute our modules, specifically because of copyrighted content > such as this for which WE have permission. YOU are not CrossWire. Any > reasonable person would conclude that he did not have permission to > distribute unless his name were, by some coincidence, "CrossWire". > Chris, you're already making modules based upon the ISV publically available (are you not?). Once you made it clear you wanted me to 'take it down' and I did - where exactly is the problem here? > > I'm curious what your train of thought was that led you to conclude that > YOU should distribute a module that we were not distributing, when your > basis for distribution was a belief that WE had permission to distribute it. > I've already explained my train of thought on this. Crosswire freely distributes version 1.5 of a module based upon ISV. One of the developers asks about updating it to include the OT. Checking the distribution rights contained in the isv.conf file, I see that Crosswire is already permitted to distribute this copyrighted text so offer to help. You ask me to remove the module from my repo - which I do. Peter gets angry and tells me to leave. > > The .conf you had posted obviously was not for that version of the module, > given that the SourceType was wrong and all of the other details simply > reflected our released version: > http://www.crosswire.org/**ftpmirror/pub/sword/raw/mods.**d/isv.conf > Perhaps, but we didn't get very far into discussions about module development before people started to exhibit 'knee-jerk' reactions. The .conf file (like all) is subject to change depending upon the needs of the module. (FYI I simply modified that .conf file incrementing the version number so it wouldn't be mistaken for the version Crosswire is already sharing with the world - this is more than a reasonable small change to make). > The basis for the module you posted was outdated at the time it was > produced and had been removed from the publisher's website by then. The > OSIS document produced from this was furthermore not valid XML (unless it > has been updated in the last year). So conversion from a Word document is > still necessary. And unless the process for converting from that Word > document can be replicated (via scripts) the whole exercise of producing > that OSIS document was without value. > > --Chris > > This is the kind of dialogue that actually gets things done, improves modules and moves things forward. I have no trouble believing what you say above and still would volunteer to do the work ... ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 4 13:39:27 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 4 Jan 2013 15:39:27 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: It's a good idea to put this in the wiki. Might I recommend (since it appeared previously on this list "Legitimate FTP Mirrors & Module Distribution Rights Question") that the following be added: "Modules specifically licensed to Crosswire may not be redistributed. For all others, as long as the license requirements are fulfilled, there is nothing preventing redistribution." This is implied from the following dialogue: On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote: >> Since Crosswire freely allows modules to be downloaded and governs the >> use of these modules afterwards through the each modules' licensing >> rights, is there something else that precludes their downstream >> redistribution so long as the original license is honoured and >> preserved? (In other words, if the licenses is established by the >> original module creator, or the license holder for the text, is >> Crosswire able to impose additional restrictions on the use of the >> text? Should it (not)?) On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings wrote: > So long as the license requirements are fulfilled, there is nothing preventing redistribution. > As I recall, the initial reaction to your announcement was not that you must take it down but > that you must filter those modules which are licensed for only Crosswire's distribution. Any > modules which are in the Public Domain or which have licenses that do not restrict their > distribution to e.g. CrossWire only, you are free to mirror. However, you would have to manually > create such a list by inspecting each module's license individually by hand. Inclusion of the above constraint (to limit redistribution to Crosswire licensed modules) would explicitly clarify Crosswire's position. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Fri Jan 4 14:06:05 2013 From: dmsmith at crosswire.org (DM Smith) Date: Fri, 4 Jan 2013 16:06:05 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: Andrew, I was careful not to say what you proposed. The quote you suggest is technically/true/correct/good as far as it goes. The other bullets I gave are why we discourage mirroring even for those. For example, in your mirror (I think you still have it available), are there any modules that are more current on the CrossWire server than in yours? Or visa versa? If someone posts to sword-support a problem with the text in a module (we get these all the time), having mirrors complicates support. We can figure out how to state it. But the way the wiki works is that everyone is welcomed to get an account and create content. Using the Talk pages is an excellent place to discuss what should be on the page. David, Chris and I moderate the content, after the fact. In Him, DM On Jan 4, 2013, at 3:39 PM, Andrew Thule wrote: > It's a good idea to put this in the wiki. Might I recommend (since it appeared previously on this list "Legitimate FTP Mirrors & Module Distribution Rights Question") that the following be added: > > "Modules specifically licensed to Crosswire may not be redistributed. For all others, as long as the license requirements are fulfilled, there is nothing preventing redistribution." > > This is implied from the following dialogue: > > On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote: > >> Since Crosswire freely allows modules to be downloaded and governs the > >> use of these modules afterwards through the each modules' licensing > >> rights, is there something else that precludes their downstream > >> redistribution so long as the original license is honoured and > >> preserved? (In other words, if the licenses is established by the > >> original module creator, or the license holder for the text, is > >> Crosswire able to impose additional restrictions on the use of the > >> text? Should it (not)?) > > On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings wrote: > > > So long as the license requirements are fulfilled, there is nothing preventing redistribution. > > As I recall, the initial reaction to your announcement was not that you must take it down but > > that you must filter those modules which are licensed for only Crosswire's distribution. Any > > modules which are in the Public Domain or which have licenses that do not restrict their > > distribution to e.g. CrossWire only, you are free to mirror. However, you would have to manually > > create such a list by inspecting each module's license individually by hand. > > > Inclusion of the above constraint (to limit redistribution to Crosswire licensed modules) would explicitly clarify Crosswire's position. > > ~A > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 4 14:18:22 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 4 Jan 2013 15:18:22 -0600 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: On Fri, Jan 4, 2013 at 3:06 PM, DM Smith wrote: > If someone posts to sword-support a problem with the text in a module (we > get these all the time), having mirrors complicates support. If Fedora can have many dozen mirrors, and Debian can have many dozen mirrors and so can every Linux distribution out there, is it so hard for us to have mirrors when it comes down to it? Each of these has requirements for what a mirror MUST, SHOULD and MAY provide and they have a vetting process when someone wants to become an official mirror they ensure that the offer follows those requirements. For the most part those requirements boil down to: provide the mandatory parts of the distribution with the same layout they have on the master, and update at minimum every X hours or days. That's hardly a burdensome task to setup, consisting mostly of a handful of options to something like rsync. If we wanted to have official mirrors we could be sure anyone offering followed those requirements and then add them to a master list of mirrors. It's not that complicated to require and it's not that complicated to configure. Many people offering to setup mirrors would already be familiar with the methods and requirements. Yes, licensing would still be an entirely different issue, but the technical implications of offering a mirror system for a pure list of files is not difficult. And certainly it's not more difficult than offering ISO images for users to download and encouraging them to be able to share them with friends! --Greg From chris at burrell.me.uk Fri Jan 4 14:34:17 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Fri, 4 Jan 2013 21:34:17 +0000 Subject: [sword-devel] [jsword-devel] StrongNumber in indexing In-Reply-To: References: Message-ID: There are two separate issues here. 1- The fact that we retrieve the closest match to a strong number is IMHO rather obscure and confusing in itself. I've hit this several times and found through rather laborious investigation that a module was using a bad strong number, or some piece of code hadn't quite formatted the number right, etc. 2- H00: The KJV is the most obvious example of a module that has/had it. It looks like someone has removed them all in the KJV2006 project ( http://www.crosswire.org/~dmsmith/kjv2006/index.html). Version 2.3 of the module still has it. Did we replace this with something else? H00 was used to indicate that the first occurrence of the strong number was the same original word as the second one. We were going to put them into the ESV. So for example Gen 2.9, used to read something like this:
Genesis 2:9 And out of the ground *made * the Lord *God * to grow [ ... ... ... some more stuff goes here ... ... ...]
In the above, this indicates that the translators split the word H06779 into "made" and into "to grow". It seems someone has removed all of these marks. However we don't have the "src" tag either so can anyone suggest how I can tell which bits go together and which bits go apart? What was the reasoning behind this change? Chris On 4 January 2013 21:07, DM Smith wrote: > H00 is not a valid Strong's number. The modules that have it should be > re-done. Do you know which are the problem modules? > > The problem with allowing H00 is that it will not find an entry in a > Strong's dictionary and will get the nearest one. Which is better? An error > filling the console or confusing the user? > > I don't mind changing the regex to be simpler, but it should not create > further problems. > > The part at the end is an optional extension. We have a module in the > wings that has it. > > In Him, > DM > > On Jan 4, 2013, at 3:34 PM, Chris Burrell wrote: > > > Hi > > > > Can I suggest a fix to the StrongNumberFilter, which currently relies on > > org.crosswire.jsword.book.study.StrongsNumber > > > > The regular expression used to match the Strong number is: > > private static final Pattern STRONGS_PATTERN = > Pattern.compile("([GgHh])0*([1-9][0-9]*)!?([A-Za-z]+)?"); > > > > Unfortunately, some texts use H00 as a strong number to indicate that > the tagged word is in 2 places (i.e. this is only the first part of the > tag). > > > > The above expression causes huge amounts of Logging to be output to the > console. > > > > I suggest we change it to something like > > > > [GgHh][0-9]+ > > > > Also, what's the stuff at the end of the regex? Haven't come across any > like that... > > > > Chris > > > > _______________________________________________ > > jsword-devel mailing list > > jsword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/jsword-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 4 14:36:45 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 4 Jan 2013 15:36:45 -0600 Subject: [sword-devel] cmake python In-Reply-To: References: <50AD9B96.9030004@gmail.com> <50BACE88.7050200@gmail.com> <50CF02B1.2050305@gmail.com> Message-ID: Ben, I just made a series of commits which further improve handling of Python builds. They do the following: 1) Move handling of bindings configuration up a directory level so CMake can include support for bindings other than SWIG in the future (unrelated to your complaint) 2) Add detection for the Python development headers and libraries that are necessary. This should leave you and anyone else wanting to build the library with bindings a little less flustered when Python is supposedly detected by CMake but not able to build. 3) Adds the ability for the user to optionally define SWORD_PYTHON_INSTALL_DIR which will be passed as an argument to --home when setup.py is invoked. These are in the tip of SVN. Let me know if they resolve that problem for you. I haven't had a chance to get your ICU fix worked out, but that's next on my list. --Greg On Sat, Dec 22, 2012 at 12:51 PM, wrote: > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings wrote: >>> On Tue, Dec 18, 2012 at 9:27 PM, wrote: >>> Here's a patch that helps some with osistest. I still get the >>> following error when I run osistest, though: >>> UTF8Transliterator: ICU: no resource index to load >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >> >> This is because it's not finding the locales or some such. I very >> frequently get it, mainly when running from an uninstalled SWORD >> instance but it happens other times even on install. >> >> I'll see about applying these patches. > > Here's patch that I think helps with the ICU support. It finds the > genrb command, and then also sets the ICU_VERSION variable, like the > configure build system does. (The osis test still fails, but it > doesn't have the UTF8Transliterator error.) > > -Ben > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From thulester at gmail.com Fri Jan 4 14:49:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 4 Jan 2013 16:49:03 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: On Fri, Jan 4, 2013 at 4:06 PM, DM Smith wrote: > Andrew, > > I was careful not to say what you proposed. The quote you suggest is > technically/true/correct/good as far as it goes. The other bullets I gave > are why we discourage mirroring even for those. > You're (licensing) reasons for wanting to manage this are also good and right (and legally required). I support what Crosswire is doing and is trying to do completely. That said, whatever you decided to do with respect to (re)distribution rights will be honoured, but it needs to be clearly communicated. If modules are not to be redistributed, impose that constraint and be transparent about it. > For example, in your mirror (I think you still have it available), are > there any modules that are more current on the CrossWire server than in > yours? Or visa versa? > All of my 'more current' modules, and other works I'm working on are in a separate private repo that does not permit anonymous access. What goes into my public repo are only those things I purposefully intend to share (primarily with you folks). With respect to modules in the mirror copied from CrossWire, you can check - they are exactly the same as at Crosswire. When a change happens at Crosswire, my mirror detects and duplicate (only) the changed modules (just like an rsync). If a module does not change, nothing happens (thus the only BW consumed is when a change occurs). You have asked me not to redistribute modules with "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire". So when the filesystem (on my end) changes, i.e. a file is copied over, the filesystem (using lsyncd) checks the contents of the file for DistributionLicense and prevents access to the ones you don't wish be redistributed. In a sense my mirror is a perfect mirror though it doesn't share those modules you don't want me to share. > If someone posts to sword-support a problem with the text in a module (we > get these all the time), having mirrors complicates support. > I don't see the problem. As mentioned linux distro mirrors do this all the time. That is why tools such as rsync and lsyncd have been created. > > We can figure out how to state it. > Simply and clearly. > > But the way the wiki works is that everyone is welcomed to get an account > and create content. Using the Talk pages is an excellent place to discuss > what should be on the page. David, Chris and I moderate the content, after > the fact. > I wouldn't mind working through some of the Beta module issues as previously mentioned, so I may just head over to the wiki. In faith. ~A > > > On Jan 4, 2013, at 3:39 PM, Andrew Thule wrote: > > It's a good idea to put this in the wiki. Might I recommend (since it > appeared previously on this list "Legitimate FTP Mirrors & Module > Distribution Rights Question") that the following be added: > > "Modules specifically licensed to Crosswire may not be redistributed. For > all others, as long as the license requirements are fulfilled, there is > nothing preventing redistribution." > > This is implied from the following dialogue: > > On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote: > >> Since Crosswire freely allows modules to be downloaded and governs the > >> use of these modules afterwards through the each modules' licensing > >> rights, is there something else that precludes their downstream > >> redistribution so long as the original license is honoured and > >> preserved? (In other words, if the licenses is established by the > >> original module creator, or the license holder for the text, is > >> Crosswire able to impose additional restrictions on the use of the > >> text? Should it (not)?) > > On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings > wrote: > > > So long as the license requirements are fulfilled, there is nothing > preventing redistribution. > > As I recall, the initial reaction to your announcement was not that you > must take it down but > > that you must filter those modules which are licensed for only > Crosswire's distribution. Any > > modules which are in the Public Domain or which have licenses that do > not restrict their > > distribution to e.g. CrossWire only, you are free to mirror. However, > you would have to manually > > create such a list by inspecting each module's license individually by > hand. > > > Inclusion of the above constraint (to limit redistribution to Crosswire > licensed modules) would explicitly clarify Crosswire's position. > > ~A > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Fri Jan 4 14:57:16 2013 From: dmsmith at crosswire.org (DM Smith) Date: Fri, 4 Jan 2013 16:57:16 -0500 Subject: [sword-devel] [jsword-devel] StrongNumber in indexing In-Reply-To: References: Message-ID: <781CE0BE-79DA-428A-8838-1264F048086A@crosswire.org> On Jan 4, 2013, at 4:34 PM, Chris Burrell wrote: > There are two separate issues here. > > 1- The fact that we retrieve the closest match to a strong number is IMHO rather obscure and confusing in itself. I've hit this several times and found through rather laborious investigation that a module was using a bad strong number, or some piece of code hadn't quite formatted the number right, etc. This is a feature of a dictionary lookup. This will typically find the longest common prefix. It'd probably be good to mark some dictionaries as exact match only. Strong's, Robinson's, and maybe daily devotions seem like candidates. > > 2- H00: The KJV is the most obvious example of a module that has/had it. It looks like someone has removed them all in the KJV2006 project (http://www.crosswire.org/~dmsmith/kjv2006/index.html). Version 2.3 of the module still has it. Did we replace this with something else? H00 was used to indicate that the first occurrence of the strong number was the same original word as the second one. We were going to put them into the ESV. > > So for example Gen 2.9, used to read something like this: > >
Genesis 2:9 > > And out > of the ground > made > the Lord > God > to grow > [ ... ... ... some more stuff goes here ... ... ...] >
> > In the above, this indicates that the translators split the word H06779 into "made" and into "to grow". > > It seems someone has removed all of these marks. However we don't have the "src" tag either so can anyone suggest how I can tell which bits go together and which bits go apart? What was the reasoning behind this change? I maintain the KJV. I couldn't find a purpose of H00. So I took it out as being wrong. If it is the splitting of words, we have a mechanism for that in the NT, which could be used. It uses src="XX" (which for the NT ties back to the XX word in the verse in a particular Greek module), the type="x-split" and subType="x-NN" where NN is a unique number w/in the verse having a value greater than the greatest value of src="XX". I'm not at all sure that subType is still needed. Both src and type are each sufficient to solve the problem. A bit more exploring to do on the KJV... > > Chris > > > > On 4 January 2013 21:07, DM Smith wrote: > H00 is not a valid Strong's number. The modules that have it should be re-done. Do you know which are the problem modules? > > The problem with allowing H00 is that it will not find an entry in a Strong's dictionary and will get the nearest one. Which is better? An error filling the console or confusing the user? > > I don't mind changing the regex to be simpler, but it should not create further problems. > > The part at the end is an optional extension. We have a module in the wings that has it. > > In Him, > DM > > On Jan 4, 2013, at 3:34 PM, Chris Burrell wrote: > > > Hi > > > > Can I suggest a fix to the StrongNumberFilter, which currently relies on > > org.crosswire.jsword.book.study.StrongsNumber > > > > The regular expression used to match the Strong number is: > > private static final Pattern STRONGS_PATTERN = Pattern.compile("([GgHh])0*([1-9][0-9]*)!?([A-Za-z]+)?"); > > > > Unfortunately, some texts use H00 as a strong number to indicate that the tagged word is in 2 places (i.e. this is only the first part of the tag). > > > > The above expression causes huge amounts of Logging to be output to the console. > > > > I suggest we change it to something like > > > > [GgHh][0-9]+ > > > > Also, what's the stuff at the end of the regex? Haven't come across any like that... > > > > Chris > > > > _______________________________________________ > > jsword-devel mailing list > > jsword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/jsword-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Fri Jan 4 14:58:23 2013 From: dmsmith at crosswire.org (DM Smith) Date: Fri, 4 Jan 2013 16:58:23 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: Regarding Fedora, I find that the mirrors differ significantly. Some have old releases, but no new releases. Some have the latest release but no updates. Some may have the alphas and/or the betas. Using yum, I have had some updates fail because they have dependencies that have not reached the mirrors that yum wants to use, making me wait a few days until the mirrors catch up. Adding in unofficial repositories complicates it even more. On Jan 4, 2013, at 4:18 PM, Greg Hellings wrote: > On Fri, Jan 4, 2013 at 3:06 PM, DM Smith wrote: >> If someone posts to sword-support a problem with the text in a module (we >> get these all the time), having mirrors complicates support. > > If Fedora can have many dozen mirrors, and Debian can have many dozen > mirrors and so can every Linux distribution out there, is it so hard > for us to have mirrors when it comes down to it? Each of these has > requirements for what a mirror MUST, SHOULD and MAY provide and they > have a vetting process when someone wants to become an official mirror > they ensure that the offer follows those requirements. > > For the most part those requirements boil down to: provide the > mandatory parts of the distribution with the same layout they have on > the master, and update at minimum every X hours or days. That's hardly > a burdensome task to setup, consisting mostly of a handful of options > to something like rsync. If we wanted to have official mirrors we > could be sure anyone offering followed those requirements and then add > them to a master list of mirrors. It's not that complicated to require > and it's not that complicated to configure. Many people offering to > setup mirrors would already be familiar with the methods and > requirements. > > Yes, licensing would still be an entirely different issue, but the > technical implications of offering a mirror system for a pure list of > files is not difficult. And certainly it's not more difficult than > offering ISO images for users to download and encouraging them to be > able to share them with friends! > > --Greg > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From christopher at burrell.me.uk Fri Jan 4 15:06:24 2013 From: christopher at burrell.me.uk (Chris Burrell) Date: Fri, 4 Jan 2013 22:06:24 +0000 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: And, a lot of the the tools using mirrors are generally addressed to a fairly technical community. The other big difference is obviously that the linux community is massive, and we are small in comparison. But I'm all up for more resilience if that's something we've had an issue with? On 4 January 2013 21:58, DM Smith wrote: > Regarding Fedora, I find that the mirrors differ significantly. Some have > old releases, but no new releases. Some have the latest release but no > updates. Some may have the alphas and/or the betas. Using yum, I have had > some updates fail because they have dependencies that have not reached the > mirrors that yum wants to use, making me wait a few days until the mirrors > catch up. Adding in unofficial repositories complicates it even more. > > > > On Jan 4, 2013, at 4:18 PM, Greg Hellings wrote: > > > On Fri, Jan 4, 2013 at 3:06 PM, DM Smith wrote: > >> If someone posts to sword-support a problem with the text in a module > (we > >> get these all the time), having mirrors complicates support. > > > > If Fedora can have many dozen mirrors, and Debian can have many dozen > > mirrors and so can every Linux distribution out there, is it so hard > > for us to have mirrors when it comes down to it? Each of these has > > requirements for what a mirror MUST, SHOULD and MAY provide and they > > have a vetting process when someone wants to become an official mirror > > they ensure that the offer follows those requirements. > > > > For the most part those requirements boil down to: provide the > > mandatory parts of the distribution with the same layout they have on > > the master, and update at minimum every X hours or days. That's hardly > > a burdensome task to setup, consisting mostly of a handful of options > > to something like rsync. If we wanted to have official mirrors we > > could be sure anyone offering followed those requirements and then add > > them to a master list of mirrors. It's not that complicated to require > > and it's not that complicated to configure. Many people offering to > > setup mirrors would already be familiar with the methods and > > requirements. > > > > Yes, licensing would still be an entirely different issue, but the > > technical implications of offering a mirror system for a pure list of > > files is not difficult. And certainly it's not more difficult than > > offering ISO images for users to download and encouraging them to be > > able to share them with friends! > > > > --Greg > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Fri Jan 4 15:07:28 2013 From: dmsmith at crosswire.org (DM Smith) Date: Fri, 4 Jan 2013 17:07:28 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: <5913CF47-52E1-4631-B7DD-894832B928EE@crosswire.org> Andrew, How do you handle modules that are removed from CrossWire? Do you use rsync w/ --delete? -- DM On Jan 4, 2013, at 4:49 PM, Andrew Thule wrote: > > > > On Fri, Jan 4, 2013 at 4:06 PM, DM Smith wrote: > Andrew, > > I was careful not to say what you proposed. The quote you suggest is technically/true/correct/good as far as it goes. The other bullets I gave are why we discourage mirroring even for those. > > You're (licensing) reasons for wanting to manage this are also good and right (and legally required). I support what Crosswire is doing and is trying to do completely. That said, whatever you decided to do with respect to (re)distribution rights will be honoured, but it needs to be clearly communicated. If modules are not to be redistributed, impose that constraint and be transparent about it. > > For example, in your mirror (I think you still have it available), are there any modules that are more current on the CrossWire server than in yours? Or visa versa? > > All of my 'more current' modules, and other works I'm working on are in a separate private repo that does not permit anonymous access. What goes into my public repo are only those things I purposefully intend to share (primarily with you folks). With respect to modules in the mirror copied from CrossWire, you can check - they are exactly the same as at Crosswire. > > When a change happens at Crosswire, my mirror detects and duplicate (only) the changed modules (just like an rsync). If a module does not change, nothing happens (thus the only BW consumed is when a change occurs). You have asked me not to redistribute modules with "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire". So when the filesystem (on my end) changes, i.e. a file is copied over, the filesystem (using lsyncd) checks the contents of the file for DistributionLicense and prevents access to the ones you don't wish be redistributed. In a sense my mirror is a perfect mirror though it doesn't share those modules you don't want me to share. > > If someone posts to sword-support a problem with the text in a module (we get these all the time), having mirrors complicates support. > > I don't see the problem. As mentioned linux distro mirrors do this all the time. That is why tools such as rsync and lsyncd have been created. > > > We can figure out how to state it. > > Simply and clearly. > > > But the way the wiki works is that everyone is welcomed to get an account and create content. Using the Talk pages is an excellent place to discuss what should be on the page. David, Chris and I moderate the content, after the fact. > > I wouldn't mind working through some of the Beta module issues as previously mentioned, so I may just head over to the wiki. > In faith. > > ~A > > > > > On Jan 4, 2013, at 3:39 PM, Andrew Thule wrote: > >> It's a good idea to put this in the wiki. Might I recommend (since it appeared previously on this list "Legitimate FTP Mirrors & Module Distribution Rights Question") that the following be added: >> >> "Modules specifically licensed to Crosswire may not be redistributed. For all others, as long as the license requirements are fulfilled, there is nothing preventing redistribution." >> >> This is implied from the following dialogue: >> >> On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote: >> >> Since Crosswire freely allows modules to be downloaded and governs the >> >> use of these modules afterwards through the each modules' licensing >> >> rights, is there something else that precludes their downstream >> >> redistribution so long as the original license is honoured and >> >> preserved? (In other words, if the licenses is established by the >> >> original module creator, or the license holder for the text, is >> >> Crosswire able to impose additional restrictions on the use of the >> >> text? Should it (not)?) >> >> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings wrote: >> >> > So long as the license requirements are fulfilled, there is nothing preventing redistribution. >> > As I recall, the initial reaction to your announcement was not that you must take it down but >> > that you must filter those modules which are licensed for only Crosswire's distribution. Any >> > modules which are in the Public Domain or which have licenses that do not restrict their >> > distribution to e.g. CrossWire only, you are free to mirror. However, you would have to manually >> > create such a list by inspecting each module's license individually by hand. >> >> >> Inclusion of the above constraint (to limit redistribution to Crosswire licensed modules) would explicitly clarify Crosswire's position. >> >> ~A >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 4 15:09:06 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 4 Jan 2013 16:09:06 -0600 Subject: [sword-devel] CMake ICU (was Re: cmake python) Message-ID: On Sat, Dec 22, 2012 at 12:51 PM, wrote: > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings wrote: >>> On Tue, Dec 18, 2012 at 9:27 PM, wrote: >>> Here's a patch that helps some with osistest. I still get the >>> following error when I run osistest, though: >>> UTF8Transliterator: ICU: no resource index to load >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >> >> This is because it's not finding the locales or some such. I very >> frequently get it, mainly when running from an uninstalled SWORD >> instance but it happens other times even on install. >> >> I'll see about applying these patches. > > Here's patch that I think helps with the ICU support. It finds the > genrb command, and then also sets the ICU_VERSION variable, like the > configure build system does. (The osis test still fails, but it > doesn't have the UTF8Transliterator error.) Your patch was on the right path but used icu-config which is horridly broken in native Windows builds (it's a Bash script) or in cross-build environments from Linux (it explodes looking for a .so library when it should look for a .dll). I have substituted using CMake's built-in pkg-config functions to pull out the modversion variable of libicuuc, which is one of the few that we actually link directly against. I wish I could tell you why that fixes the issue, but it does. Thank you much, because that has been bugging me for a long time. The fix should be in the SVN HEAD now. --Greg > > -Ben > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From chris at burrell.me.uk Fri Jan 4 15:15:52 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Fri, 4 Jan 2013 22:15:52 +0000 Subject: [sword-devel] [jsword-devel] StrongNumber in indexing In-Reply-To: <781CE0BE-79DA-428A-8838-1264F048086A@crosswire.org> References: <781CE0BE-79DA-428A-8838-1264F048086A@crosswire.org> Message-ID: Sounds good. A few notes, - the STEP interlinear functionality tries (tried?) to use this functionality to provide better interlinears. We currently don't use the x-split/or src, but could do either. - With H00, it was accepted that H00 almost always referred to the next tag, when triple tagged, it was the strong number next to H00 that was used; e.g. "H00 H1 H2" means that the next occurrence of H1 is split. Is there such a convention with x-split (there aren't that many occurrences of this, but there are a few all the same). - We were intending to include H00 in the the ESV that Tyndale are tagging. If that's not to be the case, can we decide the most appropriate way to do this? src sounds good, although sounds like it might be difficult to do properly for the KJV without a lot of manual work. We're hoping to have something ready-ish very soon. How easy would it be to restore the data via x-split? Chris On 4 January 2013 21:57, DM Smith wrote: > On Jan 4, 2013, at 4:34 PM, Chris Burrell wrote: > > There are two separate issues here. > > 1- The fact that we retrieve the closest match to a strong number is IMHO > rather obscure and confusing in itself. I've hit this several times and > found through rather laborious investigation that a module was using a bad > strong number, or some piece of code hadn't quite formatted the number > right, etc. > > > This is a feature of a dictionary lookup. This will typically find the > longest common prefix. > > It'd probably be good to mark some dictionaries as exact match only. > Strong's, Robinson's, and maybe daily devotions seem like candidates. > > > 2- H00: The KJV is the most obvious example of a module that has/had it. > It looks like someone has removed them all in the KJV2006 project ( > http://www.crosswire.org/~dmsmith/kjv2006/index.html). Version 2.3 of the > module still has it. Did we replace this with something else? H00 was used > to indicate that the first occurrence of the strong number was the same > original word as the second one. We were going to put them into the ESV. > > So for example Gen 2.9, used to read something like this: > >
Genesis 2:9 > > And out > of the ground > *made * > the Lord > *God * > to grow > [ ... ... ... some more stuff goes here ... ... ...] >
> > In the above, this indicates that the translators split the word H06779 > into "made" and into "to grow". > > It seems someone has removed all of these marks. However we don't have the > "src" tag either so can anyone suggest how I can tell which bits go > together and which bits go apart? What was the reasoning behind this change? > > > I maintain the KJV. I couldn't find a purpose of H00. So I took it out as > being wrong. If it is the splitting of words, we have a mechanism for that > in the NT, which could be used. It uses src="XX" (which for the NT ties > back to the XX word in the verse in a particular Greek module), the > type="x-split" and subType="x-NN" where NN is a unique number w/in the > verse having a value greater than the greatest value of src="XX". I'm not > at all sure that subType is still needed. Both src and type are each > sufficient to solve the problem. > > A bit more exploring to do on the KJV... > > > > Chris > > > > On 4 January 2013 21:07, DM Smith wrote: > >> H00 is not a valid Strong's number. The modules that have it should be >> re-done. Do you know which are the problem modules? >> >> The problem with allowing H00 is that it will not find an entry in a >> Strong's dictionary and will get the nearest one. Which is better? An error >> filling the console or confusing the user? >> >> I don't mind changing the regex to be simpler, but it should not create >> further problems. >> >> The part at the end is an optional extension. We have a module in the >> wings that has it. >> >> In Him, >> DM >> >> On Jan 4, 2013, at 3:34 PM, Chris Burrell wrote: >> >> > Hi >> > >> > Can I suggest a fix to the StrongNumberFilter, which currently relies on >> > org.crosswire.jsword.book.study.StrongsNumber >> > >> > The regular expression used to match the Strong number is: >> > private static final Pattern STRONGS_PATTERN = >> Pattern.compile("([GgHh])0*([1-9][0-9]*)!?([A-Za-z]+)?"); >> > >> > Unfortunately, some texts use H00 as a strong number to indicate that >> the tagged word is in 2 places (i.e. this is only the first part of the >> tag). >> > >> > The above expression causes huge amounts of Logging to be output to the >> console. >> > >> > I suggest we change it to something like >> > >> > [GgHh][0-9]+ >> > >> > Also, what's the stuff at the end of the regex? Haven't come across any >> like that... >> > >> > Chris >> > >> > _______________________________________________ >> > jsword-devel mailing list >> > jsword-devel at crosswire.org >> > http://www.crosswire.org/mailman/listinfo/jsword-devel >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 4 15:41:44 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 4 Jan 2013 17:41:44 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <5913CF47-52E1-4631-B7DD-894832B928EE@crosswire.org> References: <5913CF47-52E1-4631-B7DD-894832B928EE@crosswire.org> Message-ID: I don't actually have ssh access to CrossWire, so I'm not using the rsync protocol, rather I do have ftp access so using ftp, if a module is removed from CrossWire, the change is detected and removed from my mirror. Basically I'm using FTP to replicate RSYNC functionality, but yes - additions, changes and deletions are all reflected, otherwise the mirror would fall out of sync. (Each directory has a .listing file that helps with this book-keeping). ~A On Fri, Jan 4, 2013 at 5:07 PM, DM Smith wrote: > Andrew, > > How do you handle modules that are removed from CrossWire? Do you use > rsync w/ --delete? > > -- DM > > On Jan 4, 2013, at 4:49 PM, Andrew Thule wrote: > > > > > On Fri, Jan 4, 2013 at 4:06 PM, DM Smith wrote: > >> Andrew, >> >> I was careful not to say what you proposed. The quote you suggest is >> technically/true/correct/good as far as it goes. The other bullets I gave >> are why we discourage mirroring even for those. >> > > You're (licensing) reasons for wanting to manage this are also good and > right (and legally required). I support what Crosswire is doing and is > trying to do completely. That said, whatever you decided to do with > respect to (re)distribution rights will be honoured, but it needs to be > clearly communicated. If modules are not to be redistributed, impose that > constraint and be transparent about it. > > >> For example, in your mirror (I think you still have it available), are >> there any modules that are more current on the CrossWire server than in >> yours? Or visa versa? >> > > All of my 'more current' modules, and other works I'm working on are in a > separate private repo that does not permit anonymous access. What goes > into my public repo are only those things I purposefully intend to share > (primarily with you folks). With respect to modules in the mirror copied > from CrossWire, you can check - they are exactly the same as at Crosswire. > > When a change happens at Crosswire, my mirror detects and duplicate (only) > the changed modules (just like an rsync). If a module does not change, > nothing happens (thus the only BW consumed is when a change occurs). You > have asked me not to redistribute modules with > "DistributionLicense=Copyrighted; Permission to distribute granted to > CrossWire". So when the filesystem (on my end) changes, i.e. a file is > copied over, the filesystem (using lsyncd) checks the contents of the file > for DistributionLicense and prevents access to the ones you don't wish be > redistributed. In a sense my mirror is a perfect mirror though it doesn't > share those modules you don't want me to share. > > >> If someone posts to sword-support a problem with the text in a module (we >> get these all the time), having mirrors complicates support. >> > > I don't see the problem. As mentioned linux distro mirrors do this all > the time. That is why tools such as rsync and lsyncd have been created. > > >> >> We can figure out how to state it. >> > > Simply and clearly. > > >> >> But the way the wiki works is that everyone is welcomed to get an account >> and create content. Using the Talk pages is an excellent place to discuss >> what should be on the page. David, Chris and I moderate the content, after >> the fact. >> > > I wouldn't mind working through some of the Beta module issues as > previously mentioned, so I may just head over to the wiki. > In faith. > > ~A > > > >> >> >> On Jan 4, 2013, at 3:39 PM, Andrew Thule wrote: >> >> It's a good idea to put this in the wiki. Might I recommend (since it >> appeared previously on this list "Legitimate FTP Mirrors & Module >> Distribution Rights Question") that the following be added: >> >> "Modules specifically licensed to Crosswire may not be redistributed. >> For all others, as long as the license requirements are fulfilled, there is >> nothing preventing redistribution." >> >> This is implied from the following dialogue: >> >> On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote: >> >> Since Crosswire freely allows modules to be downloaded and governs the >> >> use of these modules afterwards through the each modules' licensing >> >> rights, is there something else that precludes their downstream >> >> redistribution so long as the original license is honoured and >> >> preserved? (In other words, if the licenses is established by the >> >> original module creator, or the license holder for the text, is >> >> Crosswire able to impose additional restrictions on the use of the >> >> text? Should it (not)?) >> >> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings >> wrote: >> >> > So long as the license requirements are fulfilled, there is nothing >> preventing redistribution. >> > As I recall, the initial reaction to your announcement was not that you >> must take it down but >> > that you must filter those modules which are licensed for only >> Crosswire's distribution. Any >> > modules which are in the Public Domain or which have licenses that do >> not restrict their >> > distribution to e.g. CrossWire only, you are free to mirror. However, >> you would have to manually >> > create such a list by inspecting each module's license individually by >> hand. >> >> >> Inclusion of the above constraint (to limit redistribution to Crosswire >> licensed modules) would explicitly clarify Crosswire's position. >> >> ~A >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 4 15:42:35 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 4 Jan 2013 17:42:35 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: References: Message-ID: I'm curious, why do people seem to prefer cmake to make? Is that a python thing? ~A On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings wrote: > On Sat, Dec 22, 2012 at 12:51 PM, wrote: > > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings > wrote: > >>> On Tue, Dec 18, 2012 at 9:27 PM, wrote: > >>> Here's a patch that helps some with osistest. I still get the > >>> following error when I run osistest, though: > >>> UTF8Transliterator: ICU: no resource index to load > >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR > >> > >> This is because it's not finding the locales or some such. I very > >> frequently get it, mainly when running from an uninstalled SWORD > >> instance but it happens other times even on install. > >> > >> I'll see about applying these patches. > > > > Here's patch that I think helps with the ICU support. It finds the > > genrb command, and then also sets the ICU_VERSION variable, like the > > configure build system does. (The osis test still fails, but it > > doesn't have the UTF8Transliterator error.) > > Your patch was on the right path but used icu-config which is horridly > broken in native Windows builds (it's a Bash script) or in cross-build > environments from Linux (it explodes looking for a .so library when it > should look for a .dll). > > I have substituted using CMake's built-in pkg-config functions to pull > out the modversion variable of libicuuc, which is one of the few that > we actually link directly against. > > I wish I could tell you why that fixes the issue, but it does. Thank > you much, because that has been bugging me for a long time. The fix > should be in the SVN HEAD now. > > --Greg > > > > > -Ben > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Fri Jan 4 17:23:16 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sat, 05 Jan 2013 00:23:16 +0000 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: <1357345396.2382.23.camel@peter-ThinkPad-X200s> On Fri, 2013-01-04 at 16:49 -0500, Andrew Thule wrote: > That said, whatever you decided to do with respect to (re)distribution > rights will be honoured, but it needs to be clearly communicated. If > modules are not to be redistributed, impose that constraint and be > transparent about it. It is clear. Your lack of respect for what is expressed in the conf file re Distribution license is your problem and not a problem of lack of clarity on our side. It is up to you to read and act upon (or rather refrain from acting) instead of us spoon feeding you (or you to demand such spoon feeding. I do strongly suggest that we will _not_ expand the Wiki. The licenses in the conf file are legal language, often written by the publisher's lawyers and can only be ignored wilfully and maliciously or by way of progressed and blind idiocy. Trying to second guess this legal language by creating a wiki page restating in our own words the content of licensing pages, explaining the often huge variability etc is liable to create confusion, confusion which then would be our responsibility. The licenses we have vary wildly. While we have endeavoured to put standard descriptive sentences on modules, this has not happened universally and many modules have individually written copyright statements. FWIW, this will also make script driven partial mirroring impossible or at least rather difficult. Peter From thulester at gmail.com Fri Jan 4 23:12:34 2013 From: thulester at gmail.com (Andrew Thule) Date: Sat, 5 Jan 2013 01:12:34 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <1357345396.2382.23.camel@peter-ThinkPad-X200s> References: <1357345396.2382.23.camel@peter-ThinkPad-X200s> Message-ID: Peter, please temper your judgement with mercy. Your claims here are neither correct nor fair. On Friday, January 4, 2013, Peter von Kaehne wrote: > On Fri, 2013-01-04 at 16:49 -0500, Andrew Thule wrote: > > It is clear. Your lack of respect for what is expressed in the conf file > re Distribution license is your problem and not a problem of lack of > clarity on our side. It is up to you to read and act upon (or rather > refrain from acting) instead of us spoon feeding you (or you to demand > such spoon feeding. > > The belief that Crosswire's license to distribute the ISV text was based upon what was contained within the isv.conf. It was not unreasonable for me to conclude therefore that additional contributions to the module would fall under the same terms. Clearly when Nic asked about updating the module, he apparently believed the same as I - specifically mentioning the OT. Perhaps, but lack of clarity on licensing constaint isn't doing this project, or its volunteers any good. The actual language of the license doesn't need to be modified for the wiki to be expanded. I've already answered this, yet still, you stand my accuser, providing no answer to my defence. Please don't make it seem like my offer to help was a lack of respect, or unreasonable. That is simply a perversion of truth. I do strongly suggest that we will _not_ expand the Wiki. The licenses > in the conf file are legal language, often written by the publisher's > lawyers and can only be ignored wilfully and maliciously or by way of > progressed and blind idiocy. > > > Trying to second guess this legal language by creating a wiki page > restating in our own words the content of licensing pages, explaining > the often huge variability etc is liable to create confusion, confusion > which then would be our responsibility. > > No ones tried to second guess any legal language. That unfounded claim is just silly (and apparently being driven by a grudge). Do you deny the ISV is currently being distributed by Crosswire, or that interest was shown by others in seeing it updated. Is there anything anywhere that suggests additional changes to that module are not currently permitted? Are there any reasonable grounds to show that an offer to provide an update to the ISV inline with the original request was unwarranted? What's causing confusion is the distorted way you are portraying my actions and motives. The licenses we have vary wildly. While we have endeavoured to put > standard descriptive sentences on modules, this has not happened > universally and many modules have individually written copyright > statements. FWIW, this will also make script driven partial mirroring > impossible or at least rather difficult. > > Well, that's patently false. As long as the .conf files accurately reflect their licenses appropriately, and those licenses remain honoured, it is a trivial thing to demonstrate accurate mirror synchronization (I can demonstrate this now) I thought the goal was to digitally propagate the Word of God as much as possible while still meeting a moral and legal obligation to safeguard copyright? Subtle hints of oligarchy manifesting itself as enthusiastic polemics against those offering help makes it seem otherwise; almost as though the goal here to stock-pile a pseudo-public repertoire of heavily licensed texts in the name of CrossWire.org, alone for the benefit of select few. The dominion of trust, more than technology, is the impediment here. Ultimately, it comes down to the project's true purposes. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Sat Jan 5 00:55:46 2013 From: chrislit at crosswire.org (Chris Little) Date: Fri, 04 Jan 2013 23:55:46 -0800 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E67843.7010308@crosswire.org> Message-ID: <50E7DC82.5020608@crosswire.org> On 1/4/2013 12:11 PM, Andrew Thule wrote: > > > On Fri, Jan 4, 2013 at 1:35 AM, Chris Little > wrote: > > We've actually had specific discussions with you about our not > wanting you to redistribute our modules, specifically because of > copyrighted content such as this for which WE have permission. YOU > are not CrossWire. Any reasonable person would conclude that he did > not have permission to distribute unless his name were, by some > coincidence, "CrossWire". > > Chris, you're already making modules based upon the ISV publically > available (are you not?). Once you made it clear you wanted me to 'take > it down' and I did - where exactly is the problem here? I credit you for taking it down, but you haven't explained why YOU felt it was YOUR place to do it in the first place. 'Andrew Thule posts the module on his FTP site' is not part of our release process. > I'm curious what your train of thought was that led you to conclude > that YOU should distribute a module that we were not distributing, > when your basis for distribution was a belief that WE had permission > to distribute it. > > I've already explained my train of thought on this. Crosswire freely > distributes version 1.5 of a module based upon ISV. One of the > developers asks about updating it to include the OT. Checking the > distribution rights contained in the isv.conf file, I see that Crosswire > is already permitted to distribute this copyrighted text so offer to > help. You ask me to remove the module from my repo - which I do. Peter > gets angry and tells me to leave. Yet, why would that have anything at all to do with you? You have no connection to the publishers, you didn't do the conversion, and you are in no way a part of the release process. You say you checked the distribution rights presented in isv.conf, but it contained exactly the string present in those modules that we have told you in the past that you may not re-distribute. You prevent reading of other such .confs on your FTP site, so you're clearly aware that this is material you should not be re-distributing. But you did it anyway, because you're content to act without thinking. --Chris From chrislit at crosswire.org Sat Jan 5 02:17:44 2013 From: chrislit at crosswire.org (Chris Little) Date: Sat, 05 Jan 2013 01:17:44 -0800 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <1357345396.2382.23.camel@peter-ThinkPad-X200s> Message-ID: <50E7EFB8.1050504@crosswire.org> On 1/4/2013 10:12 PM, Andrew Thule wrote: > Peter, please temper your judgement with mercy. Your claims here are > neither correct nor fair. So, Andrew, the fundamental problem here is that you seem to believe you are never wrong and that any disagreement is always the result of the other party being wrong. You believe you interpret the world correctly and that every other perspective is a demonstration of others' mistaken perceptions. My perspective is that you are not a rational actor. You only really seem to care about what you want and what you deem important, but you aren't particularly concerned about anything beyond the immediate term. As a result, your actions are unpredictable and frequently destructive. Whatever short-term gain you may achieve is undermined by the fact that you can't be trusted not to act at cross-purposes to CrossWire and a fair number of us perceive you as completely irrational. As a result, we can't realistically work with you. > On Friday, January 4, 2013, Peter von Kaehne wrote: > > On Fri, 2013-01-04 at 16:49 -0500, Andrew Thule wrote: > > It is clear. Your lack of respect for what is expressed in the conf file > re Distribution license is your problem and not a problem of lack of > clarity on our side. It is up to you to read and act upon (or rather > refrain from acting) instead of us spoon feeding you (or you to demand > such spoon feeding. > > > The belief that Crosswire's license to distribute the ISV text was based > upon what was contained within the isv.conf. It was not unreasonable for > me to conclude therefore that additional contributions to the module > would fall under the same terms. Clearly when Nic asked about updating > the module, he apparently believed the same as I - specifically > mentioning the OT. > > Perhaps, but lack of clarity on licensing constaint isn't doing this > project, or its volunteers any good. The actual language of the license > doesn't need to be modified for the wiki to be expanded. > > I've already answered this, yet still, you stand my accuser, providing > no answer to my defence. Please don't make it seem like my offer to > help was a lack of respect, or unreasonable. That is simply > a perversion of truth. To reiterate, the license text in the .conf, which you have admitted to reading, states: Copyrighted; Permission to distribute granted to CrossWire We've discussed the meaning of this with you before and that you are forbidden from distributing such content. You've acknowledged this before, yet you irrationally posted the ISV anyway. How does "Permission to distribute granted to CrossWire" need explanation? Along with "Copyrighted", that clearly identifies that you may not distribute, but CrossWire may. > The licenses we have vary wildly. While we have endeavoured to put > standard descriptive sentences on modules, this has not happened > universally and many modules have individually written copyright > statements. FWIW, this will also make script driven partial mirroring > impossible or at least rather difficult. > > Well, that's patently false. As long as the .conf files accurately > reflect their licenses appropriately, and those licenses > remain honoured, it is a trivial thing to demonstrate accurate mirror > synchronization (I can demonstrate this now) But you DON'T honor licenses in our modules. You ignored the license in isv.conf. > I thought the goal was to digitally propagate the Word of God as much as > possible while still meeting a moral and legal obligation to safeguard > copyright? Subtle hints of oligarchy manifesting itself as enthusiastic > polemics against those offering help makes it seem otherwise; almost as > though the goal here to stock-pile a pseudo-public repertoire of heavily > licensed texts in the name of CrossWire.org, alone for the benefit of > select few. > > The dominion of trust, more than technology, is the impediment here. > Ultimately, it comes down to the project's true purposes. One of our goals is to, as you put it, "digitally propagate the Word of God as much as possible while still meeting a moral and legal obligation to safeguard copyright". Your behavior presents a potential threat to that mission, however. You're willing to violate copyrights, which makes your presence a threat to CrossWire. You believe you simply know better and are willing to do as you please, even if it means you're violating our wishes for our materials and copyright holders' wishes for theirs. We are a community, and we value the assistance of volunteers. However, we do not appreciate actions such as yours, which defame CrossWire and threaten our ability to work with copyright holders. We want people who are willing to work with us, not against us, and sometimes that means volunteers don't get to do whatever they want. Does that mean CrossWire's leadership is going to dictate what volunteers must do? No. But it does mean we're going to dictate what volunteers must NOT do, if they wish to be part of the community. Your reckless, often illegal activities clearly mark you as someone who cannot work as part of this community. --Chris From refdoc at gmx.net Sat Jan 5 02:37:29 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sat, 05 Jan 2013 09:37:29 +0000 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <1357345396.2382.23.camel@peter-ThinkPad-X200s> Message-ID: <1357378649.2382.52.camel@peter-ThinkPad-X200s> On Sat, 2013-01-05 at 01:12 -0500, Andrew Thule wrote: > Peter, please temper your judgement with mercy. Your claims here are > neither correct nor fair. I have sent you a lengthy private reply which deals in detail with the claims that your repos are filtering out the restricted modules. Suffice to say, they do not. Please take your mirrors down, please stop claiming you do take care that you do not distribute things you should not. And please, in future, think and ask and listen. It does seem at the very least that your technical ability does not match your claimed desires. The only sensible alternative from our side is to remove you from all our mailing lists Peter -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From chris at burrell.me.uk Sat Jan 5 04:15:41 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 5 Jan 2013 11:15:41 +0000 Subject: [sword-devel] CMS volunteers required Message-ID: Hi all Just wondering if we have some CMS plugin developers on this list? STEP will expose an API to other websites, so I'm looking for volunteers to help brainstorm & possibly write the plugins for the various CMSs around. The idea is pretty straightforward at the moment, and I can think of at least 3 use cases: - Verse or passage display - Verse of the day (mainly because other people do it), but possibly also following some devotional schemes - Looking up a strong number - maybe some more things if people want to suggest more ideas. I read from http://www.siteground.com/best_cms_tools.htm that the top CMS are: - Joomla - WordPress - Drupal Any ideas if churches tend to use other popuplar CMS frameworks? STEP currently exposes a REST like interface, but some people might prefer a "javascript" include snippet to include, etc. Would be interested to hear your thoughts on that too. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael at mail.org.il Sat Jan 5 05:32:37 2013 From: michael at mail.org.il (=?UTF-8?B?157Xmdeb15DXnCDXkdeoLdeT15XXkw==?=) Date: Sat, 05 Jan 2013 14:32:37 +0200 Subject: [sword-devel] CMS volunteers required In-Reply-To: References: Message-ID: <50E81D65.3000207@mail.org.il> An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Sat Jan 5 07:50:45 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 5 Jan 2013 14:50:45 +0000 Subject: [sword-devel] CMS volunteers required In-Reply-To: <50E81D65.3000207@mail.org.il> References: <50E81D65.3000207@mail.org.il> Message-ID: Great! What kind of functionality would you want out of the box for this kind of functionality? Do you have your own website already where you'd want to include this? Would a REST API work with WordPress? or do you usually include some HTML snippet in your content? OpenScriptures people seem to have an API described here: https://github.com/openscriptures/api/wiki/RESTful-URI-Structure so it may make sense to align to that. As far as I can tell from their website, it is just a spec at the moment. But someone can correct me if I'm wrong? Chris On 5 January 2013 12:32, ????? ??-??? wrote: > I'm a WP developer and I'd like to help. > > > On 01/05/2013 01:15 PM, Chris Burrell wrote: > > Hi all > > Just wondering if we have some CMS plugin developers on this list? STEP > will expose an API to other websites, so I'm looking for volunteers to help > brainstorm & possibly write the plugins for the various CMSs around. The > idea is pretty straightforward at the moment, and I can think of at least 3 > use cases: > > - Verse or passage display > - Verse of the day (mainly because other people do it), but possibly > also following some devotional schemes > - Looking up a strong number > - maybe some more things if people want to suggest more ideas. > > I read from http://www.siteground.com/best_cms_tools.htm that the top > CMS are: > > - Joomla > - WordPress > - Drupal > > Any ideas if churches tend to use other popuplar CMS frameworks? > > STEP currently exposes a REST like interface, but some people might > prefer a "javascript" include snippet to include, etc. Would be interested > to hear your thoughts on that too. > > Chris > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cricketc at gmail.com Sat Jan 5 08:22:31 2013 From: cricketc at gmail.com (Ben) Date: Sat, 05 Jan 2013 10:22:31 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: References: Message-ID: <50E84537.1000608@gmail.com> Hey Andrew, Cmake is a replacement for autotools/configure - it still uses make. Cmake isn't related to python. The normal sequence with cmake is: cmake make make install The normal sequence otherwise is: ./configure make make install So cmake is just another way of setting up the Makefiles and build process. -Ben On 01/04/2013 05:42 PM, Andrew Thule wrote: > I'm curious, why do people seem to prefer cmake to make? Is that a > python thing? > > ~A > > > On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings > wrote: > > On Sat, Dec 22, 2012 at 12:51 PM, > wrote: > > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings > > wrote: > >>> On Tue, Dec 18, 2012 at 9:27 PM, > wrote: > >>> Here's a patch that helps some with osistest. I still get the > >>> following error when I run osistest, though: > >>> UTF8Transliterator: ICU: no resource index to load > >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR > >> > >> This is because it's not finding the locales or some such. I very > >> frequently get it, mainly when running from an uninstalled SWORD > >> instance but it happens other times even on install. > >> > >> I'll see about applying these patches. > > > > Here's patch that I think helps with the ICU support. It finds the > > genrb command, and then also sets the ICU_VERSION variable, like the > > configure build system does. (The osis test still fails, but it > > doesn't have the UTF8Transliterator error.) > > Your patch was on the right path but used icu-config which is horridly > broken in native Windows builds (it's a Bash script) or in cross-build > environments from Linux (it explodes looking for a .so library when it > should look for a .dll). > > I have substituted using CMake's built-in pkg-config functions to pull > out the modversion variable of libicuuc, which is one of the few that > we actually link directly against. > > I wish I could tell you why that fixes the issue, but it does. Thank > you much, because that has been bugging me for a long time. The fix > should be in the SVN HEAD now. > > --Greg > > > > > -Ben > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From raoul at snyman.info Sat Jan 5 08:45:35 2013 From: raoul at snyman.info (Raoul Snyman) Date: Sat, 05 Jan 2013 17:45:35 +0200 Subject: [sword-devel] CMS volunteers required In-Reply-To: References: Message-ID: <50E84A9F.8010801@snyman.info> On 05/01/2013 13:15, Chris Burrell wrote: > Just wondering if we have some CMS plugin developers on this list? > > I read from http://www.siteground.com/best_cms_tools.htm that the top > CMS are: > > * Joomla > * WordPress > * Drupal I'm not volunteering to do development (I have far too much other stuff on my hands), but I know Drupal well and I've done my fair share of Drupal module development, so if someone else is keen to do the dev on it, I'll be happy to lend guidance on how to do it. God bless, -- Raoul Snyman, B.Tech IT (Software Engineering) Saturn Laboratories m: 082 550 3754 e: raoul.snyman at saturnlaboratories.co.za w: www.saturnlaboratories.co.za b: blog.saturnlaboratories.co.za From greg.hellings at gmail.com Sat Jan 5 08:55:33 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sat, 5 Jan 2013 09:55:33 -0600 Subject: [sword-devel] CMS volunteers required In-Reply-To: References: Message-ID: Chris, A good first step might be to develop a simple library (possibly as simple as a function or a class) that fetches the data from STEP. Then you could have a single PHP class, Java class, Python class, Ruby class, etc that fetch the data from STEP and anyone could use a class like that to trivially write a plugin like you're describing. --Greg On Sat, Jan 5, 2013 at 5:15 AM, Chris Burrell wrote: > Hi all > > Just wondering if we have some CMS plugin developers on this list? STEP > will expose an API to other websites, so I'm looking for volunteers to help > brainstorm & possibly write the plugins for the various CMSs around. The > idea is pretty straightforward at the moment, and I can think of at least 3 > use cases: > > - Verse or passage display > - Verse of the day (mainly because other people do it), but possibly > also following some devotional schemes > - Looking up a strong number > - maybe some more things if people want to suggest more ideas. > > I read from http://www.siteground.com/best_cms_tools.htm that the top CMS > are: > > - Joomla > - WordPress > - Drupal > > Any ideas if churches tend to use other popuplar CMS frameworks? > > STEP currently exposes a REST like interface, but some people might prefer > a "javascript" include snippet to include, etc. Would be interested to hear > your thoughts on that too. > > Chris > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Sat Jan 5 09:03:12 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 5 Jan 2013 16:03:12 +0000 Subject: [sword-devel] CMS volunteers required In-Reply-To: References: Message-ID: Thanks Greg. Good idea! I've added that to our task tracker. I agree on the last step, but often the people using the plugins in CMSs want something that works out of the box. So it would be nice to provide these too. And in order to do so, I'd be keen to hear from people what functionality they would want in such a plugin/interface/library. Chris On 5 January 2013 15:55, Greg Hellings wrote: > Chris, > > A good first step might be to develop a simple library (possibly as simple > as a function or a class) that fetches the data from STEP. Then you could > have a single PHP class, Java class, Python class, Ruby class, etc that > fetch the data from STEP and anyone could use a class like that to > trivially write a plugin like you're describing. > > --Greg > > > On Sat, Jan 5, 2013 at 5:15 AM, Chris Burrell wrote: > >> Hi all >> >> Just wondering if we have some CMS plugin developers on this list? STEP >> will expose an API to other websites, so I'm looking for volunteers to help >> brainstorm & possibly write the plugins for the various CMSs around. The >> idea is pretty straightforward at the moment, and I can think of at least 3 >> use cases: >> >> - Verse or passage display >> - Verse of the day (mainly because other people do it), but possibly >> also following some devotional schemes >> - Looking up a strong number >> - maybe some more things if people want to suggest more ideas. >> >> I read from http://www.siteground.com/best_cms_tools.htm that the top >> CMS are: >> >> - Joomla >> - WordPress >> - Drupal >> >> Any ideas if churches tend to use other popuplar CMS frameworks? >> >> STEP currently exposes a REST like interface, but some people might >> prefer a "javascript" include snippet to include, etc. Would be interested >> to hear your thoughts on that too. >> >> Chris >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael at mail.org.il Sat Jan 5 11:54:01 2013 From: michael at mail.org.il (=?UTF-8?B?157Xmdeb15DXnCDXkdeoLdeT15XXkw==?=) Date: Sat, 05 Jan 2013 20:54:01 +0200 Subject: [sword-devel] CMS volunteers required In-Reply-To: References: <50E81D65.3000207@mail.org.il> Message-ID: <50E876C9.7070908@mail.org.il> An HTML attachment was scrubbed... URL: From cricketc at gmail.com Sat Jan 5 20:15:29 2013 From: cricketc at gmail.com (Ben) Date: Sat, 05 Jan 2013 22:15:29 -0500 Subject: [sword-devel] cmake python In-Reply-To: References: <50AD9B96.9030004@gmail.com> <50BACE88.7050200@gmail.com> <50CF02B1.2050305@gmail.com> Message-ID: <50E8EC51.4020903@gmail.com> Thanks, Greg. Both the python and icu patches work so far for me. -Ben On 01/04/2013 04:36 PM, Greg Hellings wrote: > Ben, > > I just made a series of commits which further improve handling of > Python builds. They do the following: > > 1) Move handling of bindings configuration up a directory level so > CMake can include support for bindings other than SWIG in the future > (unrelated to your complaint) > 2) Add detection for the Python development headers and libraries that > are necessary. This should leave you and anyone else wanting to build > the library with bindings a little less flustered when Python is > supposedly detected by CMake but not able to build. > 3) Adds the ability for the user to optionally define > SWORD_PYTHON_INSTALL_DIR which will be passed as an argument to --home > when setup.py is invoked. > > These are in the tip of SVN. Let me know if they resolve that problem > for you. I haven't had a chance to get your ICU fix worked out, but > that's next on my list. > > --Greg > > On Sat, Dec 22, 2012 at 12:51 PM, wrote: >> On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings wrote: >>>> On Tue, Dec 18, 2012 at 9:27 PM, wrote: >>>> Here's a patch that helps some with osistest. I still get the >>>> following error when I run osistest, though: >>>> UTF8Transliterator: ICU: no resource index to load >>>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >>> >>> This is because it's not finding the locales or some such. I very >>> frequently get it, mainly when running from an uninstalled SWORD >>> instance but it happens other times even on install. >>> >>> I'll see about applying these patches. >> >> Here's patch that I think helps with the ICU support. It finds the >> genrb command, and then also sets the ICU_VERSION variable, like the >> configure build system does. (The osis test still fails, but it >> doesn't have the UTF8Transliterator error.) >> >> -Ben >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > From thulester at gmail.com Sat Jan 5 20:38:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Sat, 5 Jan 2013 22:38:03 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: <50E84537.1000608@gmail.com> References: <50E84537.1000608@gmail.com> Message-ID: Thanks Ben. I'll have to give it a try. ~A On Saturday, January 5, 2013, Ben wrote: > Hey Andrew, > > Cmake is a replacement for autotools/configure - it still uses make. Cmake > isn't related to python. > > The normal sequence with cmake is: > cmake > make > make install > > The normal sequence otherwise is: > ./configure > make > make install > > So cmake is just another way of setting up the Makefiles and build process. > > -Ben > > On 01/04/2013 05:42 PM, Andrew Thule wrote: > >> I'm curious, why do people seem to prefer cmake to make? Is that a >> python thing? >> >> ~A >> >> >> On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings > > wrote: >> >> On Sat, Dec 22, 2012 at 12:51 PM, > > wrote: >> > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings >> > wrote: >> >>> On Tue, Dec 18, 2012 at 9:27 PM, > > wrote: >> >>> Here's a patch that helps some with osistest. I still get the >> >>> following error when I run osistest, though: >> >>> UTF8Transliterator: ICU: no resource index to load >> >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >> >> >> >> This is because it's not finding the locales or some such. I very >> >> frequently get it, mainly when running from an uninstalled SWORD >> >> instance but it happens other times even on install. >> >> >> >> I'll see about applying these patches. >> > >> > Here's patch that I think helps with the ICU support. It finds the >> > genrb command, and then also sets the ICU_VERSION variable, like >> the >> > configure build system does. (The osis test still fails, but it >> > doesn't have the UTF8Transliterator error.) >> >> Your patch was on the right path but used icu-config which is horridly >> broken in native Windows builds (it's a Bash script) or in cross-build >> environments from Linux (it explodes looking for a .so library when it >> should look for a .dll). >> >> I have substituted using CMake's built-in pkg-config functions to pull >> out the modversion variable of libicuuc, which is one of the few that >> we actually link directly against. >> >> I wish I could tell you why that fixes the issue, but it does. Thank >> you much, because that has been bugging me for a long time. The fix >> should be in the SVN HEAD now. >> >> --Greg >> >> > >> > -Ben >> > >> > ______________________________**_________________ >> > sword-devel mailing list: sword-devel at crosswire.org >> >> > http://www.crosswire.org/**mailman/listinfo/sword-devel >> > Instructions to unsubscribe/change your settings at above page >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sat Jan 5 22:50:05 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 00:50:05 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <50E7EFB8.1050504@crosswire.org> References: <1357345396.2382.23.camel@peter-ThinkPad-X200s> <50E7EFB8.1050504@crosswire.org> Message-ID: On Sat, Jan 5, 2013 at 4:17 AM, Chris Little wrote: > > So, Andrew, the fundamental problem here is that you seem to believe you > are never wrong and that any disagreement is always the result of the other > party being wrong. You believe you interpret the world correctly and that > every other perspective is a demonstration of others' mistaken perceptions. > Chris, I am wrong often, and confess it when I am. Likewise, I take responsibility for my mistakes. I'm simply asking how you (and Peter) feel I've erred. For me to be wrong about something though, means there must be something to be wrong about. To ask for clarification about one's fault is not the same as disclaiming responsbility. > > My perspective is that you are not a rational actor. You only really seem > to care about what you want and what you deem important, but you aren't > particularly concerned about anything beyond the immediate term. As a > result, your actions are unpredictable and frequently destructive. Whatever > short-term gain you may achieve is undermined by the fact that you can't be > trusted not to act at cross-purposes to CrossWire and a fair number of us > perceive you as completely irrational. As a result, we can't realistically > work with you. Then tell me what it is you want. I've already said that with respect to all Crosswire activities, I defer to your authority. I'll repeat that again for the sake of being reasonable. With respect to all Crosswire activities, I defer to your authority, completely and without argument. As a Christian I recognize that all earthly authority is ordained in heaven. To reiterate, the license text in the .conf, which you have admitted to > reading, states: > > Copyrighted; Permission to distribute granted to CrossWire > > We've discussed the meaning of this with you before and that you are > forbidden from distributing such content. You've acknowledged this before, > yet you irrationally posted the ISV anyway. > > How does "Permission to distribute granted to CrossWire" need explanation? > Along with "Copyrighted", that clearly identifies that you may not > distribute, but CrossWire may. Agreed, which is why it was removed when you asked me. So what am I missing? You say I should not have posted a updated module to my repo in response to Nics request, yet I don't have 'write' access to the Crosswire FTP server. How else would I share an update with this group? You claim this went against the License. How did it go against the license? Is the development of modules included, or not under Crosswire's permission to distribute? Are module developers on this list permitted to share copyrighted materials for the sake of development, if so, who? All? Some? None of this is documented anywhere, yet (according to you and Peter) somehow this is my fault - or I should have known? If you've outline this somewhere, and I've missed it somehow - then YES - I am at fault. Direct me to the correct URL and I will correct my defect. If not, Ill leave it up to the community to decide who is being irrational. Could you clarify, was I wrong to respond to Nics request, given that this list is public, and that Nic was trying to improve a module Crosswire already has rights on? (Or are you suggesting it was unlawful ONLY because it was ME who made the offer? (in which case you ARE making this personal)) But you DON'T honor licenses in our modules. You ignored the license in > isv.conf. Um .. no. I did as you asked when you asked. I did not ignore the license is the isv.conf, nor did I ignore your authority. Prior to that, I assumed that module development was covered because it doesn't say anywhere that it's not. So, as requested above, please clarify if developers of this list are precluded from sharing copyrighted materials amongst themselves for the purposes of module development. If not, please clarify which developers that includes (or precludes) precisely (thus addressing the concern this group is actually exclusive). > We are a community, and we value the assistance of volunteers. However, we > do not appreciate actions such as yours, which defame CrossWire and > threaten our ability to work with copyright holders. We want people who are > willing to work with us, not against us, and sometimes that means > volunteers don't get to do whatever they want. > Ok. This is a public list for development purposes, and your comments show this is somehow still personal. You've been asked to clarify whether or not this group is exclusive or open. Notwithstanding that, a member of this list asked about furthering an existing module already being distributed globally. You are suggesting MY offer to assist (made publicly on the list) was not covered under Crosswire's license (including the offer to make a newer testable module available for testing purposes). Until you come out honestly and say who can contribute and who cannot - *this is a false accusation*! If I don't know that only a select few posses rights under CrossWire's agreement, and then offer to help, you can accuse me of being irrational and of disclaiming responsibility for some fault still yet to be clarified. Look, in the interest of healing rifts, I'll assume full responsibility for my actions, and continue to honour your authority, but you've got to clarify whether or not development is covered under licensing rights and if so - who. > > Does that mean CrossWire's leadership is going to dictate what volunteers > must do? No. But it does mean we're going to dictate what volunteers must > NOT do, if they wish to be part of the community. Your reckless, often > illegal activities clearly mark you as someone who cannot work as part of > this community No offence Chris, but you and Peter have come down on me like a bag of hammers on everything I've tried to do so far. Now you're making it personal. I don't have a problem with your authority, taking responsibility, or abiding by rules, and I look forward to your clarification on who is entitled to development modules under license and who is not. However, I am no black sheep simply because I posted a possible update candidate for a module currently in distribution, for the purposes of furthering development. Similarly, I am no Judas because I did not know this was somehow prohibited. You seem to suggest I should have known, yet are curiously silent on why I should have known. Unsubstantiated accusations of such personal natures go against the claim this is an open community. It suggests hidden agendas. More concerning, they are un-Christian. Therefore, I ask that you please back such accusations with something more than bitter words. Please tell me how my response to Nics post, was unreasonable and clarify this business about module development and license. If I've erred, I'll repent and seek forgiveness. If you refuse to be explicit however, I'll expect you to stop acting the false witness. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sat Jan 5 23:02:20 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 01:02:20 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <50E7DC82.5020608@crosswire.org> References: <50E67843.7010308@crosswire.org> <50E7DC82.5020608@crosswire.org> Message-ID: On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: > > I credit you for taking it down, but you haven't explained why YOU felt it > was YOUR place to do it in the first place. 'Andrew Thule posts the module > on his FTP site' is not part of our release process. Because I was trying to help. I assumed that module development was covered under licenses, and have no other way to share modules I create with members of this list. The wiki doesn't prohibit the sharing of Copyrighted modules under development, so it was reasonable to assume since the module itself was being distributed to the word, modules being developed could be distributed also. > > Yet, why would that have anything at all to do with you? You have no > connection to the publishers, you didn't do the conversion, and you are in > no way a part of the release process. > > You say you checked the distribution rights presented in isv.conf, but it > contained exactly the string present in those modules that we have told you > in the past that you may not re-distribute. You prevent reading of other > such .confs on your FTP site, so you're clearly aware that this is material > you should not be re-distributing. But you did it anyway, because you're > content to act without thinking. I'm a member of this list, trying to help, volunteering my time, and Nic's question wasn't directed at anyone in particular. He was asking about a version of the ISV which contained the OT, which I had. Why wouldn't it have anything to do with me? Is there something somewhere that says only certain members of this list can help? Where does it say only those folks directly connected to the publisher can make improvements? Yes, as in my other response, you're still pressing away at the false idea I ignored the licenses. You still have to clarify that bit with respect to who can and who cannot offer improvements and whether or not development is excluded from 'distribution'. I was offering an improved module (and OSIS) TO Crosswire for distribution by Crosswire's repo. I admit that my thinking is limited at times. In this case it is limited by what I don't know - which is why you've been asked for clarification. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sat Jan 5 23:06:37 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 01:06:37 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E67843.7010308@crosswire.org> <50E7DC82.5020608@crosswire.org> Message-ID: Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me. I'm more than happy to remove it. As it stands now however I have done exactly what you asked when you've asked - so you should have no complaint against me. ~A On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: > > > > On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: > >> >> I credit you for taking it down, but you haven't explained why YOU felt >> it was YOUR place to do it in the first place. 'Andrew Thule posts the >> module on his FTP site' is not part of our release process. > > > Because I was trying to help. I assumed that module development was > covered under licenses, and have no other way to share modules I create > with members of this list. > > The wiki doesn't prohibit the sharing of Copyrighted modules under > development, so it was reasonable to assume since the module itself was > being distributed to the word, modules being developed could be distributed > also. > > > >> >> Yet, why would that have anything at all to do with you? You have no >> connection to the publishers, you didn't do the conversion, and you are in >> no way a part of the release process. >> >> You say you checked the distribution rights presented in isv.conf, but it >> contained exactly the string present in those modules that we have told you >> in the past that you may not re-distribute. You prevent reading of other >> such .confs on your FTP site, so you're clearly aware that this is material >> you should not be re-distributing. But you did it anyway, because you're >> content to act without thinking. > > > I'm a member of this list, trying to help, volunteering my time, and Nic's > question wasn't directed at anyone in particular. He was asking about a > version of the ISV which contained the OT, which I had. > > Why wouldn't it have anything to do with me? Is there something somewhere > that says only certain members of this list can help? Where does it say > only those folks directly connected to the publisher can make improvements? > > Yes, as in my other response, you're still pressing away at the false idea > I ignored the licenses. You still have to clarify that bit with respect to > who can and who cannot offer improvements and whether or not development is > excluded from 'distribution'. I was offering an improved module (and OSIS) > TO Crosswire for distribution by Crosswire's repo. > > I admit that my thinking is limited at times. In this case it is limited > by what I don't know - which is why you've been asked for clarification. > > ~A > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sat Jan 5 23:12:52 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 01:12:52 -0500 Subject: [sword-devel] Possible Crosswire Relationships to Publishing Industry Message-ID: Are there volunteers in this community with direct relationships to the (commercial) publishing industry? I'm asking only because it might be nice to know how commercial interests might influence this 'open' project (apart from the obvious 'we're granting Crosswire license to distribute text we have rights to'). ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 00:08:31 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Sun, 06 Jan 2013 07:08:31 +0000 Subject: [sword-devel] =?utf-8?q?ISV_status=3F?= Message-ID: Sorry for top posting. You were yesterday off list notified, with detailed evidence that you are distributing dozens and dozens of copyrighted modules for which you have no permission. There appears to be no change to that when I checked last s couple of hours ago. So your repeated on-list reassurances to be willing to follow our guidance sound hollow and thoroughly dishonest to me. Wrt submission of modules, the wiki describes the process well. To be submitted osis files are to be sent to modules at crosswire. Org. Sent from my HTC ----- Reply message ----- From: "Andrew Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 06:06 Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me. I'm more than happy to remove it. As it stands now however I have done exactly what you asked when you've asked - so you should have no complaint against me. ~A On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: I credit you for taking it down, but you haven't explained why YOU felt it was YOUR place to do it in the first place. 'Andrew Thule posts the module on his FTP site' is not part of our release process. Because I was trying to help. I assumed that module development was covered under licenses, and have no other way to share modules I create with members of this list. The wiki doesn't prohibit the sharing of Copyrighted modules under development, so it was reasonable to assume since the module itself was being distributed to the word, modules being developed could be distributed also. Yet, why would that have anything at all to do with you? You have no connection to the publishers, you didn't do the conversion, and you are in no way a part of the release process. You say you checked the distribution rights presented in isv.conf, but it contained exactly the string present in those modules that we have told you in the past that you may not re-distribute. You prevent reading of other such .confs on your FTP site, so you're clearly aware that this is material you should not be re-distributing. But you did it anyway, because you're content to act without thinking. I'm a member of this list, trying to help, volunteering my time, and Nic's question wasn't directed at anyone in particular. He was asking about a version of the ISV which contained the OT, which I had. Why wouldn't it have anything to do with me? Is there something somewhere that says only certain members of this list can help? Where does it say only those folks directly connected to the publisher can make improvements? Yes, as in my other response, you're still pressing away at the false idea I ignored the licenses. You still have to clarify that bit with respect to who can and who cannot offer improvements and whether or not development is excluded from 'distribution'. I was offering an improved module (and OSIS) TO Crosswire for distribution by Crosswire's repo. I admit that my thinking is limited at times. In this case it is limited by what I don't know - which is why you've been asked for clarification. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 00:16:33 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Sun, 06 Jan 2013 07:16:33 +0000 Subject: [sword-devel] =?utf-8?q?ISV_status=3F?= Message-ID: Sent from my HTC ----- Reply message ----- From: "refdoc at gmx.net" To: "SWORD Developers' Collaboration Forum" Subject: Re: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 07:08 Sorry for top posting. You were yesterday off list notified, with detailed evidence that you are distributing dozens and dozens of copyrighted modules for which you have no permission. There appears to be no change to that when I checked last s couple of hours ago. So your repeated on-list reassurances to be willing to follow our guidance sound hollow and thoroughly dishonest to me. Wrt submission of modules, the wiki describes the process well. To be submitted osis files are to be sent to modules at crosswire. Org. Sent from my HTC ----- Reply message ----- From: "Andrew Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 06:06 Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me. I'm more than happy to remove it. As it stands now however I have done exactly what you asked when you've asked - so you should have no complaint against me. ~A On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: I credit you for taking it down, but you haven't explained why YOU felt it was YOUR place to do it in the first place. 'Andrew Thule posts the module on his FTP site' is not part of our release process. Because I was trying to help. I assumed that module development was covered under licenses, and have no other way to share modules I create with members of this list. The wiki doesn't prohibit the sharing of Copyrighted modules under development, so it was reasonable to assume since the module itself was being distributed to the word, modules being developed could be distributed also. Yet, why would that have anything at all to do with you? You have no connection to the publishers, you didn't do the conversion, and you are in no way a part of the release process. You say you checked the distribution rights presented in isv.conf, but it contained exactly the string present in those modules that we have told you in the past that you may not re-distribute. You prevent reading of other such .confs on your FTP site, so you're clearly aware that this is material you should not be re-distributing. But you did it anyway, because you're content to act without thinking. I'm a member of this list, trying to help, volunteering my time, and Nic's question wasn't directed at anyone in particular. He was asking about a version of the ISV which contained the OT, which I had. Why wouldn't it have anything to do with me? Is there something somewhere that says only certain members of this list can help? Where does it say only those folks directly connected to the publisher can make improvements? Yes, as in my other response, you're still pressing away at the false idea I ignored the licenses. You still have to clarify that bit with respect to who can and who cannot offer improvements and whether or not development is excluded from 'distribution'. I was offering an improved module (and OSIS) TO Crosswire for distribution by Crosswire's repo. I admit that my thinking is limited at times. In this case it is limited by what I don't know - which is why you've been asked for clarification. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 00:24:28 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Sun, 06 Jan 2013 07:24:28 +0000 Subject: [sword-devel] =?utf-8?q?ISV_status=3F?= Message-ID: The public repo mirroring Crosswire is now finally down. Thanks for that. Please remove also xiphos, ibt, bible.org mirrors. Sent from my HTC ----- Reply message ----- From: "refdoc at gmx.net" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 07:16 Sent from my HTC ----- Reply message ----- From: "refdoc at gmx.net" To: "SWORD Developers' Collaboration Forum" Subject: Re: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 07:08 Sorry for top posting. You were yesterday off list notified, with detailed evidence that you are distributing dozens and dozens of copyrighted modules for which you have no permission. There appears to be no change to that when I checked last s couple of hours ago. So your repeated on-list reassurances to be willing to follow our guidance sound hollow and thoroughly dishonest to me. Wrt submission of modules, the wiki describes the process well. To be submitted osis files are to be sent to modules at crosswire. Org. Sent from my HTC ----- Reply message ----- From: "Andrew Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 06:06 Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me. I'm more than happy to remove it. As it stands now however I have done exactly what you asked when you've asked - so you should have no complaint against me. ~A On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: I credit you for taking it down, but you haven't explained why YOU felt it was YOUR place to do it in the first place. 'Andrew Thule posts the module on his FTP site' is not part of our release process. Because I was trying to help. I assumed that module development was covered under licenses, and have no other way to share modules I create with members of this list. The wiki doesn't prohibit the sharing of Copyrighted modules under development, so it was reasonable to assume since the module itself was being distributed to the word, modules being developed could be distributed also. Yet, why would that have anything at all to do with you? You have no connection to the publishers, you didn't do the conversion, and you are in no way a part of the release process. You say you checked the distribution rights presented in isv.conf, but it contained exactly the string present in those modules that we have told you in the past that you may not re-distribute. You prevent reading of other such .confs on your FTP site, so you're clearly aware that this is material you should not be re-distributing. But you did it anyway, because you're content to act without thinking. I'm a member of this list, trying to help, volunteering my time, and Nic's question wasn't directed at anyone in particular. He was asking about a version of the ISV which contained the OT, which I had. Why wouldn't it have anything to do with me? Is there something somewhere that says only certain members of this list can help? Where does it say only those folks directly connected to the publisher can make improvements? Yes, as in my other response, you're still pressing away at the false idea I ignored the licenses. You still have to clarify that bit with respect to who can and who cannot offer improvements and whether or not development is excluded from 'distribution'. I was offering an improved module (and OSIS) TO Crosswire for distribution by Crosswire's repo. I admit that my thinking is limited at times. In this case it is limited by what I don't know - which is why you've been asked for clarification. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 01:01:07 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Sun, 06 Jan 2013 08:01:07 +0000 Subject: [sword-devel] =?utf-8?q?Updating_copyrighted_modules?= Message-ID: Much of what we publish is copyrighted. We obtain detailed clear permission before anything goes on a public server. For the avoidance of doubt I describe the usual process of updating such modules. There is usually a core group member who has negotiated the exact, often highly variable terms under which we can distribute. There is usually also a direct link to a named person on the publisher's side. Occ we have permission to republish and update without new interaction, usually though not. In non English texts particularly, but others too occasionally volunteers from the wider circle are involved in negotiations and maintenance of contact. As publisher relations can be very sensitive no one outside of the people directly involved with a particular text is encouraged to do things off their own back. Sometimes it becomes obvious the our link to a publisher has gone stale. People go, companies are sold, etc. This can make obtaining permission for an updated text tricky and prolonged. Core group members know who they are and usually have a crosswire email address, though might be for all reasons or none subscribed to this list under a different one. Wider circle volunteers are encouraged to lobby for permissions when lobbying is considered useful. No one is encouraged to share copyrighted text in whatever form here on the list or in other places. If a copyrighted text has been updated, then the osis file should be emailed to Chris as per wiki, not put on the web. Chris or Troy will then check if our permissions are still ok and eventually update the module. This can all appear slow and tedious, but dealing with publishers well is crucial to what we want to achieve. Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 01:24:52 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 03:24:52 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: Peter, I've still received nothing from you. No modules currently restricted to Crosswire are available .. If I'm wrong, please identify. ~A On Sun, Jan 6, 2013 at 2:08 AM, refdoc at gmx.net wrote: > ** > Sorry for top posting. > > You were yesterday off list notified, with detailed evidence that you are > distributing dozens and dozens of copyrighted modules for which you have no > permission. > > There appears to be no change to that when I checked last s couple of > hours ago. So your repeated on-list reassurances to be willing to follow > our guidance sound hollow and thoroughly dishonest to me. > > Wrt submission of modules, the wiki describes the process well. To be > submitted osis files are to be sent to modules at crosswire. Org. > Sent from my HTC > > ----- Reply message ----- > From: "Andrew Thule" > To: "SWORD Developers' Collaboration Forum" > Subject: [sword-devel] ISV status? > Date: Sun, Jan 6, 2013 06:06 > > > Chris, I should add in response to your last comment, if you ever find I'm > distributing something I shouldn't be - please don't hesitate to tell me. > I'm more than happy to remove it. > > > As it stands now however I have done exactly what you asked when you've > asked - so you should have no complaint against me. > > ~A > > > On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: > >> >> >> >> On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: >> >>> >>> I credit you for taking it down, but you haven't explained why YOU felt >>> it was YOUR place to do it in the first place. 'Andrew Thule posts the >>> module on his FTP site' is not part of our release process. >> >> >> Because I was trying to help. I assumed that module development was >> covered under licenses, and have no other way to share modules I create >> with members of this list. >> >> The wiki doesn't prohibit the sharing of Copyrighted modules under >> development, so it was reasonable to assume since the module itself was >> being distributed to the word, modules being developed could be distributed >> also. >> >> >> >>> >>> Yet, why would that have anything at all to do with you? You have no >>> connection to the publishers, you didn't do the conversion, and you are in >>> no way a part of the release process. >>> >>> You say you checked the distribution rights presented in isv.conf, but >>> it contained exactly the string present in those modules that we have told >>> you in the past that you may not re-distribute. You prevent reading of >>> other such .confs on your FTP site, so you're clearly aware that this is >>> material you should not be re-distributing. But you did it anyway, because >>> you're content to act without thinking. >> >> >> I'm a member of this list, trying to help, volunteering my time, and >> Nic's question wasn't directed at anyone in particular. He was asking >> about a version of the ISV which contained the OT, which I had. >> >> Why wouldn't it have anything to do with me? Is there something >> somewhere that says only certain members of this list can help? Where does >> it say only those folks directly connected to the publisher can make >> improvements? >> >> Yes, as in my other response, you're still pressing away at the false >> idea I ignored the licenses. You still have to clarify that bit with >> respect to who can and who cannot offer improvements and whether or not >> development is excluded from 'distribution'. I was offering an improved >> module (and OSIS) TO Crosswire for distribution by Crosswire's repo. >> >> I admit that my thinking is limited at times. In this case it is limited >> by what I don't know - which is why you've been asked for clarification. >> >> ~A >> >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 01:33:22 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 03:33:22 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: Peter, I will honour your request with respect to the modules whose distributions are restricted to Crosswire. Please understand that the distribution rights of all modules not exclusively restricted to Crosswire are set by the Copyright owner and so as long as the licenses are being honoured you have no authority to try to control downstream usage as this list has already clarified. ~A On Sun, Jan 6, 2013 at 3:24 AM, Andrew Thule wrote: > Peter, I've still received nothing from you. No modules currently > restricted to Crosswire are available .. > > If I'm wrong, please identify. > > ~A > > > On Sun, Jan 6, 2013 at 2:08 AM, refdoc at gmx.net wrote: > >> ** >> Sorry for top posting. >> >> You were yesterday off list notified, with detailed evidence that you are >> distributing dozens and dozens of copyrighted modules for which you have no >> permission. >> >> There appears to be no change to that when I checked last s couple of >> hours ago. So your repeated on-list reassurances to be willing to follow >> our guidance sound hollow and thoroughly dishonest to me. >> >> Wrt submission of modules, the wiki describes the process well. To be >> submitted osis files are to be sent to modules at crosswire. Org. >> Sent from my HTC >> >> ----- Reply message ----- >> From: "Andrew Thule" >> To: "SWORD Developers' Collaboration Forum" >> Subject: [sword-devel] ISV status? >> Date: Sun, Jan 6, 2013 06:06 >> >> >> Chris, I should add in response to your last comment, if you ever find >> I'm distributing something I shouldn't be - please don't hesitate to tell >> me. I'm more than happy to remove it. >> >> >> As it stands now however I have done exactly what you asked when you've >> asked - so you should have no complaint against me. >> >> ~A >> >> >> On Sun, Jan 6, 2013 at 1:02 AM, Andrew Thule wrote: >> >>> >>> >>> >>> On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: >>> >>>> >>>> I credit you for taking it down, but you haven't explained why YOU felt >>>> it was YOUR place to do it in the first place. 'Andrew Thule posts the >>>> module on his FTP site' is not part of our release process. >>> >>> >>> Because I was trying to help. I assumed that module development was >>> covered under licenses, and have no other way to share modules I create >>> with members of this list. >>> >>> The wiki doesn't prohibit the sharing of Copyrighted modules under >>> development, so it was reasonable to assume since the module itself was >>> being distributed to the word, modules being developed could be distributed >>> also. >>> >>> >>> >>>> >>>> Yet, why would that have anything at all to do with you? You have no >>>> connection to the publishers, you didn't do the conversion, and you are in >>>> no way a part of the release process. >>>> >>>> You say you checked the distribution rights presented in isv.conf, but >>>> it contained exactly the string present in those modules that we have told >>>> you in the past that you may not re-distribute. You prevent reading of >>>> other such .confs on your FTP site, so you're clearly aware that this is >>>> material you should not be re-distributing. But you did it anyway, because >>>> you're content to act without thinking. >>> >>> >>> I'm a member of this list, trying to help, volunteering my time, and >>> Nic's question wasn't directed at anyone in particular. He was asking >>> about a version of the ISV which contained the OT, which I had. >>> >>> Why wouldn't it have anything to do with me? Is there something >>> somewhere that says only certain members of this list can help? Where does >>> it say only those folks directly connected to the publisher can make >>> improvements? >>> >>> Yes, as in my other response, you're still pressing away at the false >>> idea I ignored the licenses. You still have to clarify that bit with >>> respect to who can and who cannot offer improvements and whether or not >>> development is excluded from 'distribution'. I was offering an improved >>> module (and OSIS) TO Crosswire for distribution by Crosswire's repo. >>> >>> I admit that my thinking is limited at times. In this case it is >>> limited by what I don't know - which is why you've been asked for >>> clarification. >>> >>> ~A >>> >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 01:50:54 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 03:50:54 -0500 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: Message-ID: So module development IS restricted to a select and apparently secret group (who know who they are)? You have not quite been honest, transparent, or forthright in this then Peter. How was I suppose to know that was the case?; and yet you've stood my accuser knowing full well that your accusatios were unreasonable. If it is the case that certain module development is restricted ONLY to a select secret few, you should apologize for the false impressions you've left. You've false accused me publically of purposeful mischief and lawlessness. I've been acting in good faith trying to contribute on false information. I had no idea this was the case, and you certainly don't advirtise it on the site. The site makes it seem like anyone can contribute to module creation, modification. Knowing full well ONLY a select secret group of hand chosen developers are permitted to work on particular modules you've said nothing about it until now and brought into question my character and ethics knowing I was attempting to act in good faith. You cetainly had no issue with it when I was the one submitted the module, but apparently there are HUGE issues in sharing existing modules. For the sake of decency and transparency please document this in the Wiki. If it is the case that new volunteers here are only accepted for the work they can contribute, but are otherwise excluded from contributing to module improvements, make that clear too so people have reasonable expectations. Finally, do the honourable thing and acknowledge that you've not been honest in your dealing with me. A simply apology will suffice. I am forgiving. ~A On Sun, Jan 6, 2013 at 3:01 AM, refdoc at gmx.net wrote: > > Much of what we publish is copyrighted. We obtain detailed clear > permission before anything goes on a public server. For the avoidance of > doubt I describe the usual process of updating such modules. > > There is usually a core group member who has negotiated the exact, often > highly variable terms under which we can distribute. There is usually also > a direct link to a named person on the publisher's side. Occ we have > permission to republish and update without new interaction, usually though > not. In non English texts particularly, but others too occasionally > volunteers from the wider circle are involved in negotiations and > maintenance of contact. > > As publisher relations can be very sensitive no one outside of the people > directly involved with a particular text is encouraged to do things off > their own back. Sometimes it becomes obvious the our link to a publisher > has gone stale. People go, companies are sold, etc. This can make obtaining > permission for an updated text tricky and prolonged. > > Core group members know who they are and usually have a crosswire email > address, though might be for all reasons or none subscribed to this list > under a different one. Wider circle volunteers are encouraged to lobby for > permissions when lobbying is considered useful. No one is encouraged to > share copyrighted text in whatever form here on the list or in other > places. > > If a copyrighted text has been updated, then the osis file should be > emailed to Chris as per wiki, not put on the web. Chris or Troy will then > check if our permissions are still ok and eventually update the module. > > This can all appear slow and tedious, but dealing with publishers well is > crucial to what we want to achieve. > > Peter > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 01:54:32 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 03:54:32 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: I'm currently reviewing its contents to ensure no module exclusive to Crosswire was available. I will be putting it back up on completion of my review. In the meanwhile, as previously requested .. if you specifically know of any that were missed, please say so (and don't make it seem like it was purposeful. If there were a couple of missed (which I doubt) it was unintended). ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 02:13:37 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 04:13:37 -0500 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: Message-ID: Sorry, I was frustrated when I fired off that last email in hast. I would still like an apology, but I have a better idea. I think we're moving towards transparency. Since you and Chris have made my attempts to improve the ISV personal, and you've threatened a number of times to boot me off the list, and out of the community we can clear this up quickly. Please post details about the license agreement you have in place with the ISV foundation. That will both answer questions about what Crosswire's rights are and validate that Crosswire indeed has these rights. You might also wish to do this with other modules where Crosswire has exclusive distribution rights so that other developers are aware, and as you point out, sometimes copyright owners become hard to find (as you say "People go, companies are sold" ... Making your actual arrangements transparent could mean that in addition to avoiding misunderstanding like this in the future, contributors could also help track down copyright owners where problems exist. Given the gravity of the accusations you've made against me, this request is only fair as it brings to light the licensing details that confirm your claims I've done something wrong, or will exonerate me. That's fair right? ~A On Sun, Jan 6, 2013 at 3:50 AM, Andrew Thule wrote: > So module development IS restricted to a select and apparently secret > group (who know who they are)? You have not quite been honest, > transparent, or forthright in this then Peter. How was I suppose to know > that was the case?; and yet you've stood my accuser knowing full well that > your accusatios were unreasonable. > > If it is the case that certain module development is restricted ONLY to a > select secret few, you should apologize for the false impressions you've > left. You've false accused me publically of purposeful mischief and > lawlessness. I've been acting in good faith trying to contribute on false > information. I had no idea this was the case, and you certainly don't > advirtise it on the site. The site makes it seem like anyone can > contribute to module creation, modification. > > Knowing full well ONLY a select secret group of hand chosen developers are > permitted to work on particular modules you've said nothing about it until > now and brought into question my character and ethics knowing I was > attempting to act in good faith. You cetainly had no issue with it when I > was the one submitted the module, but apparently there are HUGE issues in > sharing existing modules. > > For the sake of decency and transparency please document this in the > Wiki. If it is the case that new volunteers here are only accepted for the > work they can contribute, but are otherwise excluded from contributing to > module improvements, make that clear too so people have reasonable > expectations. > > Finally, do the honourable thing and acknowledge that you've not been > honest in your dealing with me. A simply apology will suffice. I am > forgiving. > > ~A > > > > > On Sun, Jan 6, 2013 at 3:01 AM, refdoc at gmx.net wrote: > >> >> Much of what we publish is copyrighted. We obtain detailed clear >> permission before anything goes on a public server. For the avoidance of >> doubt I describe the usual process of updating such modules. >> >> There is usually a core group member who has negotiated the exact, often >> highly variable terms under which we can distribute. There is usually also >> a direct link to a named person on the publisher's side. Occ we have >> permission to republish and update without new interaction, usually though >> not. In non English texts particularly, but others too occasionally >> volunteers from the wider circle are involved in negotiations and >> maintenance of contact. >> >> As publisher relations can be very sensitive no one outside of the people >> directly involved with a particular text is encouraged to do things off >> their own back. Sometimes it becomes obvious the our link to a publisher >> has gone stale. People go, companies are sold, etc. This can make obtaining >> permission for an updated text tricky and prolonged. >> >> Core group members know who they are and usually have a crosswire email >> address, though might be for all reasons or none subscribed to this list >> under a different one. Wider circle volunteers are encouraged to lobby for >> permissions when lobbying is considered useful. No one is encouraged to >> share copyrighted text in whatever form here on the list or in other >> places. >> >> If a copyrighted text has been updated, then the osis file should be >> emailed to Chris as per wiki, not put on the web. Chris or Troy will then >> check if our permissions are still ok and eventually update the module. >> >> This can all appear slow and tedious, but dealing with publishers well is >> crucial to what we want to achieve. >> >> Peter >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 02:22:29 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Sun, 06 Jan 2013 09:22:29 +0000 Subject: [sword-devel] =?utf-8?q?ISV_status=3F?= Message-ID: When the repos were still up yesterday you had around 40 copyright restricted modules up in our Wycliffe repo and another 10 in the avraw repo. You had blocked access to the conf files in mods.d, but not to the mods.d.tar.gz and the modules folder content. In consequence of that the modules remained freely available to everyone who put your server settings into the installmgr configuration.. If you want to ensure that modules are truly gone you nerd to edit both mods.d.tar.gz and delete the relevant files in the modules subfolder. Once you have done that you will indeed be free to host our public domain or otherwise freely distributable texts. Sent from my HTC ----- Reply message ----- From: "Andrew Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 08:54 I'm currently reviewing its contents to ensure no module exclusive to Crosswire was available.? I will be putting it back up on completion of my review. In the meanwhile, as previously requested .. if you specifically know of any that were missed, please say so (and don't make it seem like it was purposeful.? If there were a couple of missed (which I doubt) it was unintended). ~A? -------------- next part -------------- An HTML attachment was scrubbed... URL: From manfred.bergmann at me.com Sun Jan 6 02:41:31 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Sun, 06 Jan 2013 10:41:31 +0100 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: Message-ID: Am 06.01.2013 um 09:50 schrieb Andrew Thule : > The site makes it seem like anyone can contribute to module creation, modification. > Anyone can contribute to module creation. If the module is finally published/released in our repos is another matter. Modification is normally only done by those people who initially created the module because they have the conversion scripts, if the text sources are in some other format that what is needed by our module utils. In principal however anyone can modify but this should be a working together with the module owner/creator. Manfred From refdoc at gmx.net Sun Jan 6 04:07:54 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sun, 06 Jan 2013 12:07:54 +0100 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: Message-ID: <20130106110754.190720@gmx.net> > Von: Manfred Bergmann > Am 06.01.2013 um 09:50 schrieb Andrew Thule : > > > The site makes it seem like anyone can contribute to module creation, > modification. > > > > Anyone can contribute to module creation. Thanks, Manfred. Indeed, anyone can. We have hundreds of modules produced by dozens of contributors. What you can not do is publish on your own server what is licensed to CrossWire. What we do not want is that people interfere in existing relationships around existing copyrighted modules. Certainly not by breaching copyright and publishing such modules on their own server. Hardly secretive cabale... Peter From refdoc at gmx.net Sun Jan 6 04:07:54 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sun, 06 Jan 2013 12:07:54 +0100 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: Message-ID: <20130106110754.190720@gmx.net> > Von: Manfred Bergmann > Am 06.01.2013 um 09:50 schrieb Andrew Thule : > > > The site makes it seem like anyone can contribute to module creation, > modification. > > > > Anyone can contribute to module creation. Thanks, Manfred. Indeed, anyone can. We have hundreds of modules produced by dozens of contributors. What you can not do is publish on your own server what is licensed to CrossWire. What we do not want is that people interfere in existing relationships around existing copyrighted modules. Certainly not by breaching copyright and publishing such modules on their own server. Hardly secretive cabale... Peter From thulester at gmail.com Sun Jan 6 06:54:59 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 08:54:59 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: I think that was a problem with only with mods.d.tar.gz only (fasly reporting them as available). Of course, I have copies of those modules, but there's nothing wrongh with that. Both the .conf file and the mods themselves were restricted, despite what mods.d.tar.gz said. Your contention is that I was 'distributing them, when I wasn't. Were you able to obtain any specifically? If so, which ones? I'm fairly confident no modules exclusively restricted to Crosswire were available from me, which means ther was (an is) no issue between us. ~A On Sunday, January 6, 2013, refdoc at gmx.net wrote: > When the repos were still up yesterday you had around 40 copyright > restricted modules up in our Wycliffe repo and another 10 in the avraw > repo. > > You had blocked access to the conf files in mods.d, but not to the > mods.d.tar.gz and the modules folder content. > > In consequence of that the modules remained freely available to everyone > who put your server settings into the installmgr configuration.. If you > want to ensure that modules are truly gone you nerd to edit both > mods.d.tar.gz and delete the relevant files in the modules subfolder. > > Once you have done that you will indeed be free to host our public domain > or otherwise freely distributable texts. > > Sent from my HTC > > ----- Reply message ----- > From: "Andrew Thule" 'thulester at gmail.com');>> > To: "SWORD Developers' Collaboration Forum" > > > Subject: [sword-devel] ISV status? > Date: Sun, Jan 6, 2013 08:54 > > > I'm currently reviewing its contents to ensure no module exclusive to > Crosswire was available. I will be putting it back up on completion of my > review. > > In the meanwhile, as previously requested .. if you specifically know of > any that were missed, please say so (and don't make it seem like it was > purposeful. If there were a couple of missed (which I doubt) it was > unintended). > > ~A > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Sun Jan 6 07:05:48 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 6 Jan 2013 14:05:48 +0000 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: <20130106110754.190720@gmx.net> References: <20130106110754.190720@gmx.net> Message-ID: I think what Andrew meant by "secretive" is that there doesn't seem to be an obvious documented place where there is a link between who owns the relationship with the copyright holder, who generated the module in the first place, and who if different is the person maintaining the module. Chris On 6 Jan 2013 11:09, "Peter von Kaehne" wrote: > > > Von: Manfred Bergmann > > > Am 06.01.2013 um 09:50 schrieb Andrew Thule : > > > > > The site makes it seem like anyone can contribute to module creation, > > modification. > > > > > > > Anyone can contribute to module creation. > > Thanks, Manfred. Indeed, anyone can. We have hundreds of modules produced > by dozens of contributors. > > What you can not do is publish on your own server what is licensed to > CrossWire. > > What we do not want is that people interfere in existing relationships > around existing copyrighted modules. Certainly not by breaching copyright > and publishing such modules on their own server. > > Hardly secretive cabale... > > Peter > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 08:21:41 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 10:21:41 -0500 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> Message-ID: Yes, exactly Chris. Both Chris and Peter have publicly accused me of breaking the law (thus tarnishing my reputation, and sullied my efforts to contribute). This implies I've breeched the terms of Crosswire's licensing agreement with the ISV foundation as the Copyright owner. What exactly is the agreement Crosswire's reached with the ISV Foundation, and what are its terms (since I've apparently broken them)? Is Crosswire's legal right to distribute Copyright text on behalf of the ISV foundation even covered by a license agreement? Does this agreement's terms extend to module developers who volunteer to assist, or not? If no such Licensing Agreement exists between the Copyright owner and Crosswire, I am not only innocent of the charges Peter and Chris have accused me of that I have broken some law, I have been falsely accused (and my reputation sullied wrongfully), but those levelling accusations against me are hypocrites for accusing me of these things, while themselves making false claims. Furthermore, if Crosswire itself doesn't have actual licensing agreements with the Copyright owners proving it possesses distribution rights, it doesn't in fact have legal right to distribute texts despite the licensing claim contained in the .conf files. In this case it has no right to castigate me for believing such a permissions exists protecting Crosswire developers (and this is also plain hypocrisy). This same logic applies to all of the modules Crosswire claims exclusive rights to. For each module this claim is made, licensing terms much exist or Crosswire is making false claims and arbitrarily using these false rights as a lever against module developers it finds less favourable. Thought Peter has not yet explicitly specified module's I've 'distributed' that belong to Crosswire, which of these actually have these rights granted through a licensing agreement. Does Crosswire in fact have exclusive right to distribute these texts (and deny others that right)? Questions like these are addressed by making public the licensing agreements (perhaps in the wiki). I can't see any reason making such licensing agreements public is a bad idea. It would only be a bad idea if Crosswire doesn't in fact have such agreements in place. As I said previously, I can see lots of benefits (including exonerating my reputation from false claims of illegality, and character assassination). If Crosswire is not willing to make pubic the agreements under which it operates, terms it claims grant it exclusive control over distribution of certain copyright texts it IS being secretive and arbitrary (Manfred). ~A On Sun, Jan 6, 2013 at 9:05 AM, Chris Burrell wrote: > I think what Andrew meant by "secretive" is that there doesn't seem to be > an obvious documented place where there is a link between who owns the > relationship with the copyright holder, who generated the module in the > first place, and who if different is the person maintaining the module. > > Chris > > > On 6 Jan 2013 11:09, "Peter von Kaehne" wrote: > >> >> > Von: Manfred Bergmann >> >> > Am 06.01.2013 um 09:50 schrieb Andrew Thule : >> > >> > > The site makes it seem like anyone can contribute to module creation, >> > modification. >> > > >> > >> > Anyone can contribute to module creation. >> >> Thanks, Manfred. Indeed, anyone can. We have hundreds of modules produced >> by dozens of contributors. >> >> What you can not do is publish on your own server what is licensed to >> CrossWire. >> >> What we do not want is that people interfere in existing relationships >> around existing copyrighted modules. Certainly not by breaching copyright >> and publishing such modules on their own server. >> >> Hardly secretive cabale... >> >> Peter >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Sun Jan 6 08:40:18 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 6 Jan 2013 10:40:18 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute Message-ID: Since this has been a controversial topic recently (and since accusations have made the matter personal), can Crosswire please post (to the wiki) the terms of its licensing agreements with each Copyright holder (on a module by module basis) so that its licensing rights are known and transparent to all? Since Crosswire is asserting these rights it must be prove it actually posses them and outline what they are (or it must forfeit the right to exercise them). Since it is holding module developers accountable to its licensing terms, it must make the license public, for the sake of transparency. Thanks. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sun Jan 6 08:45:26 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 6 Jan 2013 07:45:26 -0800 (PST) Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> Message-ID: <1357487126909-4651582.post@n4.nabble.com> There's nothing "fishy" about our distribution notices for works that are copyright. Our wiki states that copyright and distribution licensing agreements are [to be] lodged by CrossWire. The email address for all such & related communications is copyright AT crosswire DOT org. See http://crosswire.org/wiki/Copyright Where such documentation requires "snail mail" these are sent to CrossWire's registered PO Box address. CrossWire's founder keeps an archive of all such agreements to satisfy legal requirements. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Updating-copyrighted-modules-tp4651569p4651582.html Sent from the SWORD Dev mailing list archive at Nabble.com. From chris at burrell.me.uk Sun Jan 6 08:52:14 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 6 Jan 2013 15:52:14 +0000 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: <1357487126909-4651582.post@n4.nabble.com> References: <20130106110754.190720@gmx.net> <1357487126909-4651582.post@n4.nabble.com> Message-ID: My point still stands, it would be nice to know who we talk to make fixes to modules. Chris On 6 January 2013 15:45, David Haslam wrote: > There's nothing "fishy" about our distribution notices for works that are > copyright. > > Our wiki states that copyright and distribution licensing agreements are > [to > be] lodged by CrossWire. > > The email address for all such & related communications is copyright AT > crosswire DOT org. > > See http://crosswire.org/wiki/Copyright > > > Where such documentation requires "snail mail" these are sent to > CrossWire's > registered PO Box address. > > CrossWire's founder keeps an archive of all such agreements to satisfy > legal > requirements. > > > > David > > > > > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Updating-copyrighted-modules-tp4651569p4651582.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Sun Jan 6 08:55:33 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sun, 6 Jan 2013 10:55:33 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E67843.7010308@crosswire.org> <50E7DC82.5020608@crosswire.org> Message-ID: <94570A20-0658-45CB-BFD3-3DD8E409EE03@crosswire.org> Regarding module development, that wasn't the problem (though there may be other problems with that). The problem was the distribution of the developed module. Permission for CrossWire to distribute a module does not extend to its members individually. I maintain the ESV module (which is about to be released with an update). As such I cannot distribute it from my home server. It can only be distributed from the CrossWire server. Regarding module submission there are several parts to module submission that play into whether the work will be accepted: Source of the text: It has to be a primary text. Verification with sword-devel or sword-support, that the module needs to be updated and that the update would be accepted. Submission of the uncompiled module and its conf to modules at crosswire.org See http://www.crosswire.org/wiki/DevTools:Modules for more details. Regarding verification there are a variety of reasons that a module might not be accepted. Here are a few: Poor choice of source text. Poor choice of format and encoding (Bibles should be OSIS and UTF-8) Bad OSIS (TEI, ThML, ...). The module doesn't work in one or more front-ends. CrossWire doesn't have necessary permission for the module. Failure to have a repeatable process to create the module from the source. Someone else is actively working on the module. Someone else has a better text. Someone else has a repeatable process. The current maintainer of the module hasn't been in the loop. There isn't a checklist for these. I've just noticed over time that these have been reasons to reject a module. Hope this helps, DM Smith On Jan 6, 2013, at 1:02 AM, Andrew Thule wrote: > > > > On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: > > I credit you for taking it down, but you haven't explained why YOU felt it was YOUR place to do it in the first place. 'Andrew Thule posts the module on his FTP site' is not part of our release process. > > Because I was trying to help. I assumed that module development was covered under licenses, and have no other way to share modules I create with members of this list. > > The wiki doesn't prohibit the sharing of Copyrighted modules under development, so it was reasonable to assume since the module itself was being distributed to the word, modules being developed could be distributed also. > > > > Yet, why would that have anything at all to do with you? You have no connection to the publishers, you didn't do the conversion, and you are in no way a part of the release process. > > You say you checked the distribution rights presented in isv.conf, but it contained exactly the string present in those modules that we have told you in the past that you may not re-distribute. You prevent reading of other such .confs on your FTP site, so you're clearly aware that this is material you should not be re-distributing. But you did it anyway, because you're content to act without thinking. > > I'm a member of this list, trying to help, volunteering my time, and Nic's question wasn't directed at anyone in particular. He was asking about a version of the ISV which contained the OT, which I had. > > Why wouldn't it have anything to do with me? Is there something somewhere that says only certain members of this list can help? Where does it say only those folks directly connected to the publisher can make improvements? > > Yes, as in my other response, you're still pressing away at the false idea I ignored the licenses. You still have to clarify that bit with respect to who can and who cannot offer improvements and whether or not development is excluded from 'distribution'. I was offering an improved module (and OSIS) TO Crosswire for distribution by Crosswire's repo. > > I admit that my thinking is limited at times. In this case it is limited by what I don't know - which is why you've been asked for clarification. > > ~A > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Sun Jan 6 09:12:04 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sun, 6 Jan 2013 11:12:04 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: Message-ID: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> On Jan 6, 2013, at 10:40 AM, Andrew Thule wrote: > Since this has been a controversial topic recently (and since accusations have made the matter personal), can Crosswire please post (to the wiki) the terms of its licensing agreements with each Copyright holder (on a module by module basis) so that its licensing rights are known and transparent to all? No, we cannot publish the terms of licensing agreements. Think about it. These are confidential, privileged contracts between organizations. > > Since Crosswire is asserting these rights it must be prove it actually posses them and outline what they are (or it must forfeit the right to exercise them). Since it is holding module developers accountable to its licensing terms, it must make the license public, for the sake of transparency. The contracts are dictated by the publishers. When asked what they need to say, we provide the broadest description of what they need to say at minimum, but we don't ever suggest particular wording or terms. If the terms are unacceptable to us, we communicate that clearly and let them either amend their terms or withdraw the module. We only need to prove our assertion with the publishers. Which we have do on occasion. The wording of your request is inviting a "go pound sand" response. Please be careful in how you word things. In Him, DM From scribe at crosswire.org Sun Jan 6 09:23:59 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sun, 06 Jan 2013 17:23:59 +0100 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: Message-ID: <50E9A51F.6050508@crosswire.org> Dear Andrew, We previously had a volunteer manage and keep certain details of copyright information (contact, lead, etc.) up at: http://crosswire.org/sword/copyright/ The volunteer has moved on to other things away from CrossWire and this site is no longer kept current so we don't link to these pages any longer. Regarding the actual license agreements with publishers, these are not something that we would publish online. Often publishers have agreements with many organizations and work out different agreements with different organizations. Some pay fees; some do not. We have had agreements where we have volunteers pay nominal fees to keep our agreements current. Publisher expect this information to remain confidential. This is typical. For example, when Logos distributes a work freely or for a fee to an end user, they never publish their actual agreement with the publisher which states how much Logos pays per module or per annum for the rights to make material available to their users. It would violate the publisher's trust. Granted, the majority of our agreements probably have nothing anyone would mind being made public, but I am not willing to make those judgments. If a publisher challenges our right to distribute their text, I will certainly make our agreement available to them, but not to end users who challenge our right to distribute a work. If they feel they have legitimate reasons for doubting we have permission, they should inform the publisher who can take action if they also feel the same. I'm not encouraging you to inform publishers that we might not have the right to distribute modules; in fact, most of this thread has been because we are highly sensitive to honor publisher agreements. We give publishers a choice of what they would like displayed to the end user. We ask them to choose from our list here: http://crosswire.org/wiki/DevTools:conf_Files#DistributionLicense They feel this is clear: *Copyrighted; Permission to distribute granted to CrossWire * No other public distribution should be made. I understand your heart to help by publicly making a text available to a developer, and also for the mirrors. I appreciate your desire to help. Please know that when it comes to violating copyright, we desire to avoid even the appearance of evil. A work available on a public website (for any purpose, however good) which is not authorized by the publisher of the text, is against our policy. I appreciate that you've removed the text and are working to be sure you are no longer mirroring our other content which is licensed by us exclusively for distribution by CrossWire. This is most appreciated, and I hope this is all simply a misunderstanding and that wounds can heal and we can share in positive work together. Troy On 01/06/2013 04:40 PM, Andrew Thule wrote: > Since this has been a controversial topic recently (and since > accusations have made the matter personal), can Crosswire please post > (to the wiki) the terms of its licensing agreements with each > Copyright holder (on a module by module basis) so that its licensing > rights are known and transparent to all? > > Since Crosswire is asserting these rights it must be prove it actually > posses them and outline what they are (or it must forfeit the right to > exercise them). Since it is holding module developers accountable to > its licensing terms, it must make the license public, for the sake of > transparency. > > Thanks. > > ~A > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Sun Jan 6 09:38:00 2013 From: chrislit at crosswire.org (Chris Little) Date: Sun, 06 Jan 2013 08:38:00 -0800 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> Message-ID: <50E9A868.8070805@crosswire.org> Andrew, we've already established that you just plainly don't understand copyright. You think it simply doesn't apply to you if you don't feel like having it apply to you. That's why you are still hosting illegally produced copies of translations of the Dead Sea Scrolls. We established this a while back. I believe we have exactly zero exclusive licenses to distribute content. If we had an exclusive license for a translation, that would indicate that no one else could have a license to distribute that translation. (It's common to limit exclusivity to a particular domain, so many translations will have exclusive print publishing licenses but non-exclusive electronic publishing licenses so that material can appear in various electronic formats.) We don't pretend that we have exclusive control over any content (except arguably that content which we have produced ourselves). That control obviously resides with the copyright holder. That is the essence of copyright. So, when we direct you to not redistribute content on your server, it's because you're breaking the law by doing so. The distribution rights that we negotiate are rights that have been granted to CrossWire and do not transfer to others unless the copyright holder explicitly permits it. --Chris On 1/6/2013 7:21 AM, Andrew Thule wrote: > Yes, exactly Chris. > > Both Chris and Peter have publicly accused me of breaking the law (thus > tarnishing my reputation, and sullied my efforts to contribute). This > implies I've breeched the terms of Crosswire's licensing agreement with > the ISV foundation as the Copyright owner. What exactly is the > agreement Crosswire's reached with the ISV Foundation, and what are its > terms (since I've apparently broken them)? Is Crosswire's legal right > to distribute Copyright text on behalf of the ISV foundation even > covered by a license agreement? Does this agreement's terms extend to > module developers who volunteer to assist, or not? If no such Licensing > Agreement exists between the Copyright owner and Crosswire, I am not > only innocent of the charges Peter and Chris have accused me of that I > have broken some law, I have been falsely accused (and my reputation > sullied wrongfully), but those levelling accusations against me are > hypocrites for accusing me of these things, while themselves making > false claims. > > Furthermore, if Crosswire itself doesn't have actual licensing > agreements with the Copyright owners proving it possesses distribution > rights, it doesn't in fact have legal right to distribute texts despite > the licensing claim contained in the .conf files. In this case it has > no right to castigate me for believing such a permissions exists > protecting Crosswire developers (and this is also plain hypocrisy). This > same logic applies to all of the modules Crosswire claims exclusive > rights to. For each module this claim is made, licensing terms much > exist or Crosswire is making false claims and arbitrarily using these > false rights as a lever against module developers it finds less favourable. > > Thought Peter has not yet explicitly specified module's I've > 'distributed' that belong to Crosswire, which of these actually have > these rights granted through a licensing agreement. Does Crosswire in > fact have exclusive right to distribute these texts (and deny others > that right)? Questions like these are addressed by making public the > licensing agreements (perhaps in the wiki). I can't see any reason > making such licensing agreements public is a bad idea. It would only be > a bad idea if Crosswire doesn't in fact have such agreements in place. > As I said previously, I can see lots of benefits (including exonerating > my reputation from false claims of illegality, and character > assassination). If Crosswire is not willing to make pubic the > agreements under which it operates, terms it claims grant it exclusive > control over distribution of certain copyright texts it IS being > secretive and arbitrary (Manfred). > > ~A > > > On Sun, Jan 6, 2013 at 9:05 AM, Chris Burrell > wrote: > > I think what Andrew meant by "secretive" is that there doesn't seem > to be an obvious documented place where there is a link between who > owns the relationship with the copyright holder, who generated the > module in the first place, and who if different is the person > maintaining the module. > > Chris > > > On 6 Jan 2013 11:09, "Peter von Kaehne" > wrote: > > > > Von: Manfred Bergmann > > > > Am 06.01.2013 um 09:50 schrieb Andrew Thule > >: > > > > > The site makes it seem like anyone can contribute to > module creation, > > modification. > > > > > > > Anyone can contribute to module creation. > > Thanks, Manfred. Indeed, anyone can. We have hundreds of modules > produced by dozens of contributors. > > What you can not do is publish on your own server what is > licensed to CrossWire. > > What we do not want is that people interfere in existing > relationships around existing copyrighted modules. Certainly not > by breaching copyright and publishing such modules on their own > server. > > Hardly secretive cabale... > > Peter > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From chrislit at crosswire.org Sun Jan 6 09:47:07 2013 From: chrislit at crosswire.org (Chris Little) Date: Sun, 06 Jan 2013 08:47:07 -0800 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> <1357487126909-4651582.post@n4.nabble.com> Message-ID: <50E9AA8B.4040903@crosswire.org> On 1/6/2013 7:52 AM, Chris Burrell wrote: > My point still stands, it would be nice to know who we talk to make > fixes to modules. Some submitters elect to sign their modules in the .conf file. Check there for a name and/or email address. In lieu of that, email me at modules at crosswire.org and I can let you know. In most cases I would be the point of contact anyway, either by virtue of having produced the current release or because I've taken responsibility for orphaned content. For minor bugs, report through the bug tracker. --Chris From chris at burrell.me.uk Sun Jan 6 10:05:12 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 6 Jan 2013 17:05:12 +0000 Subject: [sword-devel] Finding out copyright programatically Message-ID: Hi Can I suggest adding something in the module configuration and/or sword/jsword backends that could indicate what kind of copyright we're dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. I personally would find that useful if I want to make available public domain resources in some fashion to others, and thereby not include some of the copyrighted material. For example, if I'm going to allow people to include hooks into STEP to obtain and display the Scriptures on their websites, I'd want to make sure I can sift through the texts that I make available and the ones that I don't (see my separate thread about CMSses) I guess this could be as trivial as looking for "Public domain" or "Copyright" in the field in the configuration, but in the numerous emails from the last few days, someone said something along the lines that we were trying to be consistent but aren't always. If, we think, this is consistent enough, I'd be happy to implement a simple getter on the BookMetadata object in JSword. If we don't think this is valuable and the .conf files aren't consistent, I'll simply maintain an "opt-in" list for those resources that are public domain + those I've obtained permissions from Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 10:32:22 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sun, 06 Jan 2013 18:32:22 +0100 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> Message-ID: <20130106173222.27500@gmx.net> I guess this is going nowhere as so many discussions with you in the past. 1) If I mistakenly accused you of anything you have not done I am quite obviously very sorry. But so far it does not look that way, does it? 2) On the 5th of January at about 9 am GMT I sent you an email detailing the steps I took to verify that you are indeed distributing copyrighted modules, whether by accident or wilfully I did not hazard to guess. This very detailed email was sent at roughly the same time as an email to list which gave the generic info. You should have it. In both places I asked you to take the server down and sort things. Instead of taking the server down you continued to run the server and claim you carefully vetted things that nothing was distributed which should not. By continuing with this claim, despite detailed info being sent personally to you and generic info on the list things did not get better. Eventually you took this morning the repo down. I thanked you for that. You still though have many other modules up for which you are essentially in the same position as you were with ours, unless you got explicit permissions. Right now I drilled down through the IBT repo of yours with the browser and downloaded both several of the Adyge module files as also several conf files. The conf files also starkly declare the modules as copyrighted, at which point you would require a permission. If you have got one from IBT I am pleased for you. If not you got a problem. You would be then distributing illegally material owned by IBT. They might let you do so or they might pursue you. I simply warn you. 3) Wrt our rights - these are quite obviously not exclusive and you also quite obviously did not breach _our_ agreements. So there is little point to see our agreements with anyone. Your broke the law as you are not part of CrossWire and hence have no permission from anyone to publish ISV or any other copyrighted and CrossWire restricted module I could download from your server. You also - and this is where we came in - sullied our reputation by your - however tenuous - association with us and by posting on our list links to your repos. 4) Wrt secret cabale - not so. The mailing list archive is public and it is entirely clear but to the dullest who is in charge and who is not. Your perception of having become a member of CrossWire -------- Original-Nachricht -------- > Datum: Sun, 6 Jan 2013 10:21:41 -0500 > Von: Andrew Thule > An: Chris Burrell , "SWORD Developers\' Collaboration Forum" > Betreff: Re: [sword-devel] Updating copyrighted modules > Yes, exactly Chris. > > Both Chris and Peter have publicly accused me of breaking the law (thus > tarnishing my reputation, and sullied my efforts to contribute). This > implies I've breeched the terms of Crosswire's licensing agreement with > the > ISV foundation as the Copyright owner. What exactly is the agreement > Crosswire's reached with the ISV Foundation, and what are its terms (since > I've apparently broken them)? Is Crosswire's legal right to distribute > Copyright text on behalf of the ISV foundation even covered by a license > agreement? Does this agreement's terms extend to module developers who > volunteer to assist, or not? If no such Licensing Agreement exists between > the Copyright owner and Crosswire, I am not only innocent of the charges > Peter and Chris have accused me of that I have broken some law, I have > been falsely accused (and my reputation sullied wrongfully), but those > levelling accusations against me are hypocrites for accusing me of these > things, while themselves making false claims. > > Furthermore, if Crosswire itself doesn't have actual licensing agreements > with the Copyright owners proving it possesses distribution rights, it > doesn't in fact have legal right to distribute texts despite the licensing > claim contained in the .conf files. In this case it has no right to > castigate me for believing such a permissions exists protecting Crosswire > developers (and this is also plain hypocrisy). This same logic applies to > all of the modules Crosswire claims exclusive rights to. For each module > this claim is made, licensing terms much exist or Crosswire is making > false > claims and arbitrarily using these false rights as a lever against module > developers it finds less favourable. > > Thought Peter has not yet explicitly specified module's I've 'distributed' > that belong to Crosswire, which of these actually have these rights > granted > through a licensing agreement. Does Crosswire in fact have exclusive > right > to distribute these texts (and deny others that right)? Questions like > these are addressed by making public the licensing agreements (perhaps in > the wiki). I can't see any reason making such licensing agreements public > is a bad idea. It would only be a bad idea if Crosswire doesn't in fact > have such agreements in place. As I said previously, I can see lots of > benefits (including exonerating my reputation from false claims of > illegality, and character assassination). If Crosswire is not willing to > make pubic the agreements under which it operates, terms it claims grant > it > exclusive control over distribution of certain copyright texts it IS being > secretive and arbitrary (Manfred). > > ~A > > > On Sun, Jan 6, 2013 at 9:05 AM, Chris Burrell wrote: > > > I think what Andrew meant by "secretive" is that there doesn't seem to > be > > an obvious documented place where there is a link between who owns the > > relationship with the copyright holder, who generated the module in the > > first place, and who if different is the person maintaining the module. > > > > Chris > > > > > > On 6 Jan 2013 11:09, "Peter von Kaehne" wrote: > > > >> > >> > Von: Manfred Bergmann > >> > >> > Am 06.01.2013 um 09:50 schrieb Andrew Thule : > >> > > >> > > The site makes it seem like anyone can contribute to module > creation, > >> > modification. > >> > > > >> > > >> > Anyone can contribute to module creation. > >> > >> Thanks, Manfred. Indeed, anyone can. We have hundreds of modules > produced > >> by dozens of contributors. > >> > >> What you can not do is publish on your own server what is licensed to > >> CrossWire. > >> > >> What we do not want is that people interfere in existing relationships > >> around existing copyrighted modules. Certainly not by breaching > copyright > >> and publishing such modules on their own server. > >> > >> Hardly secretive cabale... > >> > >> Peter > >> > >> _______________________________________________ > >> sword-devel mailing list: sword-devel at crosswire.org > >> http://www.crosswire.org/mailman/listinfo/sword-devel > >> Instructions to unsubscribe/change your settings at above page > >> > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > From jhphx at cox.net Sun Jan 6 11:27:31 2013 From: jhphx at cox.net (jhphx) Date: Sun, 06 Jan 2013 11:27:31 -0700 Subject: [sword-devel] ISV status? In-Reply-To: References: Message-ID: <50E9C213.5060301@cox.net> On 1/6/2013 1:54 AM, Andrew Thule wrote: > I'm currently reviewing its contents to ensure no module exclusive to > Crosswire was available. I will be putting it back up on completion > of my review. > ... I am not sure how you think being exclusive to Crosswire works in this context, but, IF: a) none of those other sources have legitimate (licensed) copies of a copyrighted text or it's derivatives, OR b) none of those sources provided you with a legitimate license to do whatever you do, OR c) it simply appears like you are violating anyone's copyrights, THEN: It won't matter to CrossWire how many other sources there are, you would appear to be, and in fact could be, a threat to CrossWire's ability to distribute if it appears that CrossWire is condoning what you do. It does not matter how the other sources see it, or how you see it, it matters how it seems to CrossWire and how it may seem to the publishers they work with. Andrew, you appear to want to help. There are many things someone like you could do, but maybe working on copyrighted modules and distribution of them is not the right task for now. There remains many other things needing to be done. If you still feel the need to work on a copyrighted text for CrossWire then I suggest you ask yourself three things: a) could this work produce a copy, new copy, new version, or derivative of the text, b) could this work result in exposing, intentionally or not, a copy so that wild (any unlicensed) distribution could result, c) could this work possibly offend CrossWire or the publishers they work with. If the answer to any of those is yes then ask if you should work on it and exactly how you should do it to avoid these problems. Although, at this time "just ask" may be the best policy. Just a suggestion, I am not an official voice on these matters. Jerry From dmsmith at crosswire.org Sun Jan 6 11:33:41 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sun, 6 Jan 2013 13:33:41 -0500 Subject: [sword-devel] Updating copyrighted modules In-Reply-To: References: <20130106110754.190720@gmx.net> <1357487126909-4651582.post@n4.nabble.com> Message-ID: <610B2FB4-8DFA-4B5E-989F-03E3E8F14C8B@crosswire.org> The typical way is to ask on the list. It is possible an old module is an orphan. There are several ways a module is orphaned: The source for the module is no longer available. The module maintainer is no longer willing/able/available to work on the module. This is true regarding any module, especially non-copyrighted module. Regarding a copyrighted module, I'll share how I became involved in being the pumpkin holder for such: I made small contributions that demonstrated my understanding of SWORD/JSword/CrossWire's mission and purpose. At some point the number and quality of these contributions was sufficient to warrant getting commit privs to the JSword project. I volunteered for the KJV update and did a good job on it. When the ESV came along, I volunteered for that. I didn't put my name on it, nor did I on the KJV, but it is not hard to find out. I'm just the servant. In Him, DM On Jan 6, 2013, at 10:52 AM, Chris Burrell wrote: > My point still stands, it would be nice to know who we talk to make fixes to modules. > > Chris > > > > On 6 January 2013 15:45, David Haslam wrote: > There's nothing "fishy" about our distribution notices for works that are > copyright. > > Our wiki states that copyright and distribution licensing agreements are [to > be] lodged by CrossWire. > > The email address for all such & related communications is copyright AT > crosswire DOT org. > > See http://crosswire.org/wiki/Copyright > > > Where such documentation requires "snail mail" these are sent to CrossWire's > registered PO Box address. > > CrossWire's founder keeps an archive of all such agreements to satisfy legal > requirements. > > > > David > > > > > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/Updating-copyrighted-modules-tp4651569p4651582.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Sun Jan 6 12:17:27 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sun, 6 Jan 2013 14:17:27 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: A few more reasons we discourage mirroring: SWORD and JSword have no means for managing mirrors. They expect each repository to be a unique collection of modules. A mirror that is partial, not containing all that is in the master repository, probably will be confusing to users. A mirror that is hosted along with questionable modules probably will give the appearance that CrossWire condones those modules. Especially when the modules are in the same repository. In Him, DM On Jan 4, 2013, at 9:09 AM, DM Smith wrote: > From time to time, interest has been expressed in mirroring CrossWire's SWORD modules. I thought I'd reiterate our policy. > > We strongly, very strongly, discourage mirroring of the SWORD module repository. > > Those modules for which CrossWire has obtained distribution permission from copyright holders must not be mirrored. These have "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire" in their conf. CrossWire maintains correspondence for each of these modules. > > Mirrors are seldom current/correct, despite intentions. > > On occasion we have unintentionally hosted modules for which we did not have permission. When presented with an ownership claim, we typically will take the module offline immediately and validate the claim. If the claim is false, we will put the module back up. If the claim is true, we obtain permission before putting the module back online or we don't put it back. This is an important part of our stewardship. > > If or when CrossWire has problems with distribution, we'll tackle the problem at that time. Probably with a "Content Delivery Network" of CrossWire owned servers. > > This or some variation of this probably should be in the wiki. > > In His Service, > DM > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Sun Jan 6 12:29:47 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sun, 06 Jan 2013 20:29:47 +0100 Subject: [sword-devel] SFTP Support In-Reply-To: References: <50D7DC71.1040002@crosswire.org> <50E10268.4040505@crosswire.org> Message-ID: <50E9D0AB.7010801@crosswire.org> Applied. Thanks Greg, for the original contribution and for taking the time to work through the details. On 12/31/2012 03:53 PM, Greg Hellings wrote: > Here is the updated patch adding CURLSFTPAVAILABLE support to CMake as > well as to the library code. It defaults to assuming no SFTP support > if either the curl-config executable cannot be found or if it returns > a value other than "1" from the quick detection process we have > settled on. > > Users of Windows builds through either VisualStudio or Borland will > need to figure out if curl-config is available on their systems and, > if not, come up with another way to detect and support SFTP for > clients using those builds. On Linux it is a Bash script, so it might > be adaptable to Manfred's XCode system in some way also. > > For those in the JSword world, I am sure there are SFTP Java clients > available which could be leveraged if they wanted to add support for > the same functionality to JSword applications. > > --Greg > > On Sun, Dec 30, 2012 at 9:11 PM, Troy A. Griffitts wrote: >> OK Greg, >> >> I've hacked detection of CURL SFTP into the autotools build (hopefully-- it >> works for me). >> >> I've added a new compile time define with -DCURLSFTPAVAILABLE to go along >> with the existing -DCURLAVAILABLE >> >> If you'd like to update the sftp patch to conditionally compile support in >> based on this define, that would be cool. I'll do it myself soon if you >> don't have time. >> >> Troy >> >> >> >> On 12/28/2012 11:42 AM, Greg Hellings wrote: >>> Further digging with help from our friends has revealed this nugget: >>> >>> $ curl-config --protocols >>> >>> produces a newline-delimited list of protocols that the particular >>> build of libcurl supports. curl-config is a shell script which can be >>> run on the build system and should satisfy both the requirements of >>> native builds and cross-compiling support. We could use this to set a >>> compiler macro indicating support (or not) for SFTP in the target >>> libcurl library. >>> >>> If someone wants to tackle that in the autotools world, I can add >>> detection to CMake as well. A simple command such as >>> $ curl-config --protocols | grep SFTP | wc -l >>> 1 >>> >>> in Fedora will result in a value of 1 or greater if SFTP is supported >>> while it should produce 0 if SFTP support is left out. An Ubuntu >>> system produce this output: >>> $ curl-config --protocols | grep SFTP | wc -l >>> 0 >>> >>> And it even works for cross-compiling: >>> $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols | >>> grep SFTP | wc -l >>> 1 >>> >>> >>> This appears to be our best way forward if we want to enable >>> compile-time enabling or disabling of this option. >>> >>> --Greg >>> >>> On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings >>> wrote: >>>> Troy, >>>> >>>> On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts >>>> wrote: >>>>> Dear Greg, >>>>> >>>>> Looking to apply this SFTP patch, could you give me some background as >>>>> to >>>>> why the check to ignore across all transports for '.' and '..'? >>>> Our downloading method runs recursively from the given directory until >>>> it runs out of directory depth. FTP servers don't usually seem to >>>> return . and .. as valid paths, and the HTTP(S) transport attempts to >>>> parse the returned HTML page to avoid the link to the parent >>>> directory. But whatever options are passed by cURL to the SFTP >>>> transport resulted in it returning . and .. as paths within the >>>> current directory. Because '.' came first in the list, the installmgr >>>> was running through an infinite loop whenever it tried to pull data >>>> from the server. >>>> >>>> I added it at the level of all transports because we don't want to >>>> either loop infinitely on '.' or accidentally pull a whole server >>>> recursively by following '..' to the root of the server. It might be a >>>> server config option that permits it, but I wanted to avoid the >>>> possibility of the InlstallMgr class getting choked up on it. >>>> >>>> --Greg >>>> >>>>> Thanks, >>>>> >>>>> Troy >>>>> >>>>> >>>>> >>>>> >>>>> On 12/03/2012 04:06 PM, Greg Hellings wrote: >>>>> >>>>> The attached patch will introduce support for SFTPSource transports in >>>>> the SWORD engine, allowing a user to access remote repositories over >>>>> SFTP (which is enabled by default when a user enables SSH). >>>>> >>>>> --Greg >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 14:39:28 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sun, 06 Jan 2013 22:39:28 +0100 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: Message-ID: <20130106213928.65330@gmx.net> > Von: Chris Burrell > Can I suggest adding something in the module configuration and/or > sword/jsword backends that could indicate what kind of copyright we're > dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. As such this is simply a call to see some conf entry, is it not? The only caveat would be that the conf entry might not be present and something sensible (i.e. something which stops you using a module inadvertently) needs to be returned. The next question is interpretation of the result - rights for distribution of a unchanged module e.g. would prevent using it in a webserver. Rights to create derivates non-commercially would preclude having e.g. ads on the screen. Maybe one of the best solutions (not sure if this is feasible) would be to return a bit encoded byte value which summarises Copyright - yes/no Distributable as unchanged module yes/no Distributable as derivate yes/no Commercial yes/no For a church website without ads, only the third value would be relevant. For someone who wants to create CDs with modules to give away or sale, 2 and 4 would be relevant. Does this cover what you were thinking of? Peter From niccarter at mac.com Sun Jan 6 14:52:00 2013 From: niccarter at mac.com (Nic Carter) Date: Mon, 07 Jan 2013 08:52:00 +1100 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: <04F3B10D-ABDC-453B-AB06-77B53CA4F742@mac.com> Sorry for the top post, but I believe the below text (by Chris Burrell) sums things up pretty well ? there is no problem with people having personal mirrors of all the CrossWire modules, for personal use only and not for public access. However, at this point there isn't a major issue with resilience & hence there is no need at this point in time for mirrors. If there were (in the future?), we could then discuss on this list the best way to move forward, but I believe it would then involve working on libsword to help properly handle this, code that currently doesn't exist. That time isn't now, so we don't need to discuss how to go about this at this point in time. Regarding public mirrors now, if ppl must have their own mirrors (cause they want one for whatever reasons?), they are free to do so as long as it's not the copyrighted material, as people have been pointing out. However, if you _must_ have your own (legal & public) mirror, I suggest it's probably best not to publicly advertise it here! Privately inform people about them if you must. That way we can hopefully avoid confusion for users for if they do a duckduckgo search (or google search) & find your repo & wonder why there are multiple modules of the same name, etc... Just my random thoughts... :) Sent from my phone, hence this email may be short... On 05/01/2013, at 9:06, Chris Burrell wrote: > But I'm all up for more resilience if that's something we've had an issue with? From chris at burrell.me.uk Sun Jan 6 15:01:07 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 6 Jan 2013 22:01:07 +0000 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: <20130106213928.65330@gmx.net> References: <20130106213928.65330@gmx.net> Message-ID: Yes, this is exactly what I was thinking and has more complexity than I had originally thought of - very helpful. I guess the next question, is whether your four categories are comprehensive? We would perhaps want to include another bit to indicate that there are special non-parseable conditions, so as to indicate to a developer that he'll have to work out what it means for him. I'm thinking for example of texts that someone makes available on condition that they are not displayed/used alongside other texts from different publishers, or other kind of special permissions. What do you mean by "rights for distribution of an unchanged module"? Do you mean that someone accessing the module through a front-end, in this case a web server, would not be included in the licence? i.e. because the web server has made modifications to the way the data is displayed? I guess the one thing that I'm not quite clear on yet which affects the above discussion, is what where the distribution licence ends and where a license to use the distributed module in Sword frontends starts/ends. Say, a Xiphos user gets a module distributed by CrossWire, such as the ESV. Does the Xiphos user then need to seek permission to use the module through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to seek permission from Crossway? Possibly? Just trying to get my head around the Copyright and licensing law which I find rather complicated. Chris On 6 January 2013 21:39, Peter von Kaehne wrote: > > > Von: Chris Burrell > > > Can I suggest adding something in the module configuration and/or > > sword/jsword backends that could indicate what kind of copyright we're > > dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. > > As such this is simply a call to see some conf entry, is it not? > > The only caveat would be that the conf entry might not be present and > something sensible (i.e. something which stops you using a module > inadvertently) needs to be returned. > > The next question is interpretation of the result - rights for > distribution of a unchanged module e.g. would prevent using it in a > webserver. Rights to create derivates non-commercially would preclude > having e.g. ads on the screen. > > Maybe one of the best solutions (not sure if this is feasible) would be to > return a bit encoded byte value which summarises > > Copyright - yes/no > Distributable as unchanged module yes/no > Distributable as derivate yes/no > Commercial yes/no > > For a church website without ads, only the third value would be relevant. > For someone who wants to create CDs with modules to give away or sale, 2 > and 4 would be relevant. > > Does this cover what you were thinking of? > > Peter > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Sun Jan 6 15:11:50 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sun, 06 Jan 2013 23:11:50 +0100 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: <20130106213928.65330@gmx.net> Message-ID: <20130106221150.94840@gmx.net> > Von: Chris Burrell > I guess the next question, is whether your four categories are > comprehensive? We would perhaps want to include another bit to indicate > that there are special non-parseable conditions, so as to indicate to a > developer that he'll have to work out what it means for him. I'm thinking > for example of texts that someone makes available on condition that they > are not displayed/used alongside other texts from different publishers, or > other kind of special permissions. Yes, makes sense. And there may be more. > What do you mean by "rights for distribution of an unchanged module"? Do > you mean that someone accessing the module through a front-end, in this > case a web server, would not be included in the licence? i.e. because the > web server has made modifications to the way the data is displayed? Quite a few modules of ours can be distributed as modules, unchanged, e.g. you can pack them on a CD and pass on. But you could not create a new module with them, to add e.g. strongs and then distribute the result. Or, indeed, you could not use them to power a webserver. > I guess the one thing that I'm not quite clear on yet which affects the > above discussion, is what where the distribution licence ends and where a > license to use the distributed module in Sword frontends starts/ends. As soon as you display for others you have moved from using to distributing. So a module to power your private intranet swordweb install is fine. but the same module might not be used for running a public swordweb or e.g. a webapi for people to "bible-power" their blogs. I have not paid much attention to what you are doing, but I guess that is what you are about, no? Say, > a Xiphos user gets a module distributed by CrossWire, such as the ESV. > Does > the Xiphos user then need to seek permission to use the module through > Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to seek > permission from Crossway? Possibly? I do not understand that... Does CrossWay remotely start up on my computer Xiphos and feed it bible references for me to peruse? That should be fine. It is my use for myself. > > Just trying to get my head around the Copyright and licensing law which I > find rather complicated. It is. But the basic rule applies - if others come into it you start distributing. And short of that you can do a lot or at least no one will really object. Even in the UK where there is no fair use. Peter > > > > From chris at burrell.me.uk Sun Jan 6 15:27:45 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 6 Jan 2013 22:27:45 +0000 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: <20130106221150.94840@gmx.net> References: <20130106213928.65330@gmx.net> <20130106221150.94840@gmx.net> Message-ID: Thanks Peter. That helps a lot. Powering other people's websites is a nice to have for us. Step is one product, which runs as a desktop application (using a local embedded web server), but also will run on the web. We've already sought licence agreements from Crossway (the ESV copyright holders) and others to cover this. But the above helps me (I haven't been part of the discussions between Tyndale and the various copyright holders). Chris On 6 January 2013 22:11, Peter von Kaehne wrote: > > > Von: Chris Burrell > > > I guess the next question, is whether your four categories are > > comprehensive? We would perhaps want to include another bit to indicate > > that there are special non-parseable conditions, so as to indicate to a > > developer that he'll have to work out what it means for him. I'm thinking > > for example of texts that someone makes available on condition that they > > are not displayed/used alongside other texts from different publishers, > or > > other kind of special permissions. > > Yes, makes sense. And there may be more. > > > > What do you mean by "rights for distribution of an unchanged module"? Do > > you mean that someone accessing the module through a front-end, in this > > case a web server, would not be included in the licence? i.e. because the > > web server has made modifications to the way the data is displayed? > > Quite a few modules of ours can be distributed as modules, unchanged, e.g. > you can pack them on a CD and pass on. But you could not create a new > module with them, to add e.g. strongs and then distribute the result. Or, > indeed, you could not use them to power a webserver. > > > I guess the one thing that I'm not quite clear on yet which affects the > > above discussion, is what where the distribution licence ends and where a > > license to use the distributed module in Sword frontends starts/ends. > > As soon as you display for others you have moved from using to > distributing. > > So a module to power your private intranet swordweb install is fine. but > the same module might not be used for running a public swordweb or e.g. a > webapi for people to "bible-power" their blogs. > > I have not paid much attention to what you are doing, but I guess that is > what you are about, no? > > > > Say, > > a Xiphos user gets a module distributed by CrossWire, such as the ESV. > > Does > > the Xiphos user then need to seek permission to use the module through > > Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to > seek > > permission from Crossway? Possibly? > > I do not understand that... Does CrossWay remotely start up on my computer > Xiphos and feed it bible references for me to peruse? That should be fine. > It is my use for myself. > > > > Just trying to get my head around the Copyright and licensing law which I > > find rather complicated. > > It is. But the basic rule applies - if others come into it you start > distributing. And short of that you can do a lot or at least no one will > really object. Even in the UK where there is no fair use. > > Peter > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Sun Jan 6 15:59:04 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sun, 6 Jan 2013 17:59:04 -0500 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: Message-ID: Yes. o.c.j.book.BookMetaData is the proper place for this. There are many of ways you can do it. There are several patterns in the class already. I'll leave the choice up to you. As Peter mentioned there are (at least) two questions that need to be answered: Redistributable? Are there modules that cannot be distributed at all. Commercial? Are there modules that preclude the use in a commercial context. (E.g. Ad driven). Note, when STEP is a desktop application or a web application, these might have different meanings. Here are details of how to dig it out today: o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE defines the list of acceptable values. You can access this via o.c.j.book.BookMetadata.getProperty as in: o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName()) You can then compare it to expected values as in "Copyrighted; Permission to distribute granted to CrossWire" Hope this helps. In Him, DM On Jan 6, 2013, at 12:05 PM, Chris Burrell wrote: > Hi > > Can I suggest adding something in the module configuration and/or sword/jsword backends that could indicate what kind of copyright we're dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. > > I personally would find that useful if I want to make available public domain resources in some fashion to others, and thereby not include some of the copyrighted material. > > For example, if I'm going to allow people to include hooks into STEP to obtain and display the Scriptures on their websites, I'd want to make sure I can sift through the texts that I make available and the ones that I don't (see my separate thread about CMSses) > > I guess this could be as trivial as looking for "Public domain" or "Copyright" in the field in the configuration, but in the numerous emails from the last few days, someone said something along the lines that we were trying to be consistent but aren't always. > > If, we think, this is consistent enough, I'd be happy to implement a simple getter on the BookMetadata object in JSword. > > If we don't think this is valuable and the .conf files aren't consistent, I'll simply maintain an "opt-in" list for those resources that are public domain + those I've obtained permissions from > Chris > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From thulester at gmail.com Mon Jan 7 10:31:27 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 12:31:27 -0500 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: Message-ID: I think this is a fanstastic idea, the idea of progamatically being able to detect Status of a module programatically! Very good suggestion. On this example: "Say, a Xiphos user gets a module distributed by CrossWire, such as the ESV. Does the Xiphos user then need to seek permission to use the module through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to seek permission from Crossway? Possibly?" This is also a good example. Crossway as the Copyright Owner has granted CrossWire license to distribute the text as a Sword modules, so the terms of this license (permission) that govern how this works should be covered in a license agreemnt (that defines things like 'Distribute', the scope of what CrossWire means (develoepers or certain individuals) etc. So 'license to use' the ESV module has been set by the copyright owner, but CrossWire should be able to clarify what that means programatically as the licensee but also display the terms of the license (publicy) since (presumably) it has already been worked out with Crossway and both parties understand what it means. ~A On Sun, Jan 6, 2013 at 5:59 PM, DM Smith wrote: > Yes. o.c.j.book.BookMetaData is the proper place for this. There are many > of ways you can do it. There are several patterns in the class already. > I'll leave the choice up to you. > > As Peter mentioned there are (at least) two questions that need to be > answered: > Redistributable? Are there modules that cannot be distributed at all. > Commercial? Are there modules that preclude the use in a commercial > context. (E.g. Ad driven). > > Note, when STEP is a desktop application or a web application, these might > have different meanings. > > Here are details of how to dig it out today: > > o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE > defines the list of acceptable values. > > You can access this via o.c.j.book.BookMetadata.getProperty as in: > > > o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName()) > > You can then compare it to expected values as in "Copyrighted; Permission > to distribute granted to CrossWire" > > Hope this helps. > > In Him, > DM > > On Jan 6, 2013, at 12:05 PM, Chris Burrell wrote: > > > Hi > > > > Can I suggest adding something in the module configuration and/or > sword/jsword backends that could indicate what kind of copyright we're > dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. > > > > I personally would find that useful if I want to make available public > domain resources in some fashion to others, and thereby not include some of > the copyrighted material. > > > > For example, if I'm going to allow people to include hooks into STEP to > obtain and display the Scriptures on their websites, I'd want to make sure > I can sift through the texts that I make available and the ones that I > don't (see my separate thread about CMSses) > > > > I guess this could be as trivial as looking for "Public domain" or > "Copyright" in the field in the configuration, but in the numerous emails > from the last few days, someone said something along the lines that we were > trying to be consistent but aren't always. > > > > If, we think, this is consistent enough, I'd be happy to implement a > simple getter on the BookMetadata object in JSword. > > > > If we don't think this is valuable and the .conf files aren't > consistent, I'll simply maintain an "opt-in" list for those resources that > are public domain + those I've obtained permissions from > > Chris > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 10:31:55 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 12:31:55 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <1357378649.2382.52.camel@peter-ThinkPad-X200s> References: <1357345396.2382.23.camel@peter-ThinkPad-X200s> <1357378649.2382.52.camel@peter-ThinkPad-X200s> Message-ID: Peter, I've not received your email yet, but look forward to it. Let me address your concern. I have no intention of distributing modules exclusively licensed to Crosswire. I think I currently am, however (as I previously said to Chris) I invent you to contact me with concerns and request. I look forward to, and welcome your input, with the additional promise that I will ensure no modules exclusively licensed to Crosswire are obtainable from me. I hope this move us towards reconciliation. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 10:39:26 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 12:39:26 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: DM, I agree that not having thought through mirror management procedurally (policy and best backpractice) is reason enough to hold off on such a venture, but those problems are typically trivial to solve given effective communication. Since technology is subordinat to intent, what needs to be worked out to move forward along these lines is the clarification of intent. If I were to look back on this recent discussion, I'd suggest a number of principles are already clear: -CrossWire resevers the right to approve or deny mirrors -CrossWire reserves the right to define which repositorories are considered "root" repositories (so authoritive) -Distribution of modules exclusively licensed to CrossWire should be retained by Crosswire -All Mirrors should take no longer than x (period of time) to accurately reflect 'root repositories' Etc. This issues have already (to some extent) been hashed through in debate, however discussion on the matter was limited, unproductive and unclear simply because of the degree of hostility the 'idea' of mirrors alone produced. If there had been an attitude of 'open but undecided' reservation about the matter, rather than outright 'hostility' its likely the issues you are raising now could have been dealt with more readily. ~A On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: > A few more reasons we discourage mirroring: > SWORD and JSword have no means for managing mirrors. They expect each > repository to be a unique collection of modules. > > A mirror that is partial, not containing all that is in the master > repository, probably will be confusing to users. > > A mirror that is hosted along with questionable modules probably will give > the appearance that CrossWire condones those modules. Especially when the > modules are in the same repository. > > In Him, > DM > > On Jan 4, 2013, at 9:09 AM, DM Smith wrote: > > From time to time, interest has been expressed in mirroring CrossWire's > SWORD modules. I thought I'd reiterate our policy. > > We strongly, very strongly, discourage mirroring of the SWORD module > repository. > > Those modules for which CrossWire has obtained distribution permission > from copyright holders must not be mirrored. These have > "DistributionLicense=Copyrighted; Permission to distribute granted to > CrossWire" in their conf. CrossWire maintains correspondence for each of > these modules. > > Mirrors are seldom current/correct, despite intentions. > > On occasion we have unintentionally hosted modules for which we did not > have permission. When presented with an ownership claim, we typically will > take the module offline immediately and validate the claim. If the claim is > false, we will put the module back up. If the claim is true, we obtain > permission before putting the module back online or we don't put it back. > This is an important part of our stewardship. > > If or when CrossWire has problems with distribution, we'll tackle the > problem at that time. Probably with a "Content Delivery Network" of > CrossWire owned servers. > > This or some variation of this probably should be in the wiki. > > In His Service, > DM > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 10:41:56 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 12:41:56 -0500 Subject: [sword-devel] SFTP Support In-Reply-To: <50E9D0AB.7010801@crosswire.org> References: <50D7DC71.1040002@crosswire.org> <50E10268.4040505@crosswire.org> <50E9D0AB.7010801@crosswire.org> Message-ID: Is there a URL that oultines what this patch does? I agree this is going to be very useful change, but confess - I don't yet understand what this patch is doing . (Also, thanks indeed Greg for your efforts) ~A On Sun, Jan 6, 2013 at 2:29 PM, Troy A. Griffitts wrote: > Applied. Thanks Greg, for the original contribution and for taking the > time to work through the details. > > > On 12/31/2012 03:53 PM, Greg Hellings wrote: > > Here is the updated patch adding CURLSFTPAVAILABLE support to CMake as > well as to the library code. It defaults to assuming no SFTP support > if either the curl-config executable cannot be found or if it returns > a value other than "1" from the quick detection process we have > settled on. > > Users of Windows builds through either VisualStudio or Borland will > need to figure out if curl-config is available on their systems and, > if not, come up with another way to detect and support SFTP for > clients using those builds. On Linux it is a Bash script, so it might > be adaptable to Manfred's XCode system in some way also. > > For those in the JSword world, I am sure there are SFTP Java clients > available which could be leveraged if they wanted to add support for > the same functionality to JSword applications. > > --Greg > > On Sun, Dec 30, 2012 at 9:11 PM, Troy A. Griffitts wrote: > > OK Greg, > > I've hacked detection of CURL SFTP into the autotools build (hopefully-- it > works for me). > > I've added a new compile time define with -DCURLSFTPAVAILABLE to go along > with the existing -DCURLAVAILABLE > > If you'd like to update the sftp patch to conditionally compile support in > based on this define, that would be cool. I'll do it myself soon if you > don't have time. > > Troy > > > > On 12/28/2012 11:42 AM, Greg Hellings wrote: > > Further digging with help from our friends has revealed this nugget: > > $ curl-config --protocols > > produces a newline-delimited list of protocols that the particular > build of libcurl supports. curl-config is a shell script which can be > run on the build system and should satisfy both the requirements of > native builds and cross-compiling support. We could use this to set a > compiler macro indicating support (or not) for SFTP in the target > libcurl library. > > If someone wants to tackle that in the autotools world, I can add > detection to CMake as well. A simple command such as > $ curl-config --protocols | grep SFTP | wc -l > 1 > > in Fedora will result in a value of 1 or greater if SFTP is supported > while it should produce 0 if SFTP support is left out. An Ubuntu > system produce this output: > $ curl-config --protocols | grep SFTP | wc -l > 0 > > And it even works for cross-compiling: > $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols | > grep SFTP | wc -l > 1 > > > This appears to be our best way forward if we want to enable > compile-time enabling or disabling of this option. > > --Greg > > On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings > wrote: > > Troy, > > On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts wrote: > > Dear Greg, > > Looking to apply this SFTP patch, could you give me some background as > to > why the check to ignore across all transports for '.' and '..'? > > Our downloading method runs recursively from the given directory until > it runs out of directory depth. FTP servers don't usually seem to > return . and .. as valid paths, and the HTTP(S) transport attempts to > parse the returned HTML page to avoid the link to the parent > directory. But whatever options are passed by cURL to the SFTP > transport resulted in it returning . and .. as paths within the > current directory. Because '.' came first in the list, the installmgr > was running through an infinite loop whenever it tried to pull data > from the server. > > I added it at the level of all transports because we don't want to > either loop infinitely on '.' or accidentally pull a whole server > recursively by following '..' to the root of the server. It might be a > server config option that permits it, but I wanted to avoid the > possibility of the InlstallMgr class getting choked up on it. > > --Greg > > > Thanks, > > Troy > > > > > On 12/03/2012 04:06 PM, Greg Hellings wrote: > > The attached patch will introduce support for SFTPSource transports in > the SWORD engine, allowing a user to access remote repositories over > SFTP (which is enabled by default when a user enables SSH). > > --Greg > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 10:47:44 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 12:47:44 -0500 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: Message-ID: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> The CrossWire (SWORD/JSword based) "desktop" applications may download and use any module provided by CrossWire. There is no need for these applications to know or care what the license is. All modules are fair game. Applications that serve the web, such as SwordWEB and are not hosted on the CrossWire server can only serve those modules to which they are legally entitled to. It doesn't matter what the details of the license agreement are with CrossWire, those organizations must obtain their own license agreements. The need that STEP has for checking is that it can be used to serve the WEB or be a desktop application. In the one case it cares; in the other, it doesn't. So far we have left it to the user of the application to do the right thing. In Him, DM On Jan 7, 2013, at 12:31 PM, Andrew Thule wrote: > I think this is a fanstastic idea, the idea of progamatically being able to detect Status of a module programatically! Very good suggestion. > > On this example: > > "Say, a Xiphos user gets a module distributed by CrossWire, such as the ESV. Does the Xiphos user then need to seek permission to use the module through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to seek permission from Crossway? Possibly?" > > This is also a good example. > > Crossway as the Copyright Owner has granted CrossWire license to distribute the text as a Sword modules, so the terms of this license (permission) that govern how this works should be covered in a license agreemnt (that defines things like 'Distribute', the scope of what CrossWire means (develoepers or certain individuals) etc. > > So 'license to use' the ESV module has been set by the copyright owner, but CrossWire should be able to clarify what that means programatically as the licensee but also display the terms of the license (publicy) since (presumably) it has already been worked out with Crossway and both parties understand what it means. > > ~A > > > > > On Sun, Jan 6, 2013 at 5:59 PM, DM Smith wrote: > Yes. o.c.j.book.BookMetaData is the proper place for this. There are many of ways you can do it. There are several patterns in the class already. I'll leave the choice up to you. > > As Peter mentioned there are (at least) two questions that need to be answered: > Redistributable? Are there modules that cannot be distributed at all. > Commercial? Are there modules that preclude the use in a commercial context. (E.g. Ad driven). > > Note, when STEP is a desktop application or a web application, these might have different meanings. > > Here are details of how to dig it out today: > > o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE > defines the list of acceptable values. > > You can access this via o.c.j.book.BookMetadata.getProperty as in: > > o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName()) > > You can then compare it to expected values as in "Copyrighted; Permission to distribute granted to CrossWire" > > Hope this helps. > > In Him, > DM > > On Jan 6, 2013, at 12:05 PM, Chris Burrell wrote: > > > Hi > > > > Can I suggest adding something in the module configuration and/or sword/jsword backends that could indicate what kind of copyright we're dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. > > > > I personally would find that useful if I want to make available public domain resources in some fashion to others, and thereby not include some of the copyrighted material. > > > > For example, if I'm going to allow people to include hooks into STEP to obtain and display the Scriptures on their websites, I'd want to make sure I can sift through the texts that I make available and the ones that I don't (see my separate thread about CMSses) > > > > I guess this could be as trivial as looking for "Public domain" or "Copyright" in the field in the configuration, but in the numerous emails from the last few days, someone said something along the lines that we were trying to be consistent but aren't always. > > > > If, we think, this is consistent enough, I'd be happy to implement a simple getter on the BookMetadata object in JSword. > > > > If we don't think this is valuable and the .conf files aren't consistent, I'll simply maintain an "opt-in" list for those resources that are public domain + those I've obtained permissions from > > Chris > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 10:55:11 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 12:55:11 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: Mirror management is a moot issue if the software doesn't support mirrors. I have no plans to add such to JSword, unless it is added to SWORD first. I highly doubt that it will be added to SWORD until a problem with resiliency creates a real need. Even then, I'm not sure that that will be used as a solution. In His Service, DM On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: > DM, I agree that not having thought through mirror management procedurally (policy and best backpractice) is reason enough to hold off on such a venture, but those problems are typically trivial to solve given effective communication. > > Since technology is subordinat to intent, what needs to be worked out to move forward along these lines is the clarification of intent. > > If I were to look back on this recent discussion, I'd suggest a number of principles are already clear: > -CrossWire resevers the right to approve or deny mirrors > -CrossWire reserves the right to define which repositorories are considered "root" repositories (so authoritive) > -Distribution of modules exclusively licensed to CrossWire should be retained by Crosswire > -All Mirrors should take no longer than x (period of time) to accurately reflect 'root repositories' > > Etc. > This issues have already (to some extent) been hashed through in debate, however discussion on the matter was limited, unproductive and unclear simply because of the degree of hostility the 'idea' of mirrors alone produced. > > If there had been an attitude of 'open but undecided' reservation about the matter, rather than outright 'hostility' its likely the issues you are raising now could have been dealt with more readily. > > ~A > > > On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: > A few more reasons we discourage mirroring: > SWORD and JSword have no means for managing mirrors. They expect each repository to be a unique collection of modules. > > A mirror that is partial, not containing all that is in the master repository, probably will be confusing to users. > > A mirror that is hosted along with questionable modules probably will give the appearance that CrossWire condones those modules. Especially when the modules are in the same repository. > > In Him, > DM > > On Jan 4, 2013, at 9:09 AM, DM Smith wrote: > >> From time to time, interest has been expressed in mirroring CrossWire's SWORD modules. I thought I'd reiterate our policy. >> >> We strongly, very strongly, discourage mirroring of the SWORD module repository. >> >> Those modules for which CrossWire has obtained distribution permission from copyright holders must not be mirrored. These have "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire" in their conf. CrossWire maintains correspondence for each of these modules. >> >> Mirrors are seldom current/correct, despite intentions. >> >> On occasion we have unintentionally hosted modules for which we did not have permission. When presented with an ownership claim, we typically will take the module offline immediately and validate the claim. If the claim is false, we will put the module back up. If the claim is true, we obtain permission before putting the module back online or we don't put it back. This is an important part of our stewardship. >> >> If or when CrossWire has problems with distribution, we'll tackle the problem at that time. Probably with a "Content Delivery Network" of CrossWire owned servers. >> >> This or some variation of this probably should be in the wiki. >> >> In His Service, >> DM >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 10:58:15 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 12:58:15 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: No, we cannot publish the terms of licensing agreements. Think about it. > These are confidential, privileged contracts between organizations. > Umm, with software Licenses, Acceptable Use Policies, Copyright Restrictions and Copyright limitations are not typically priviledge .. The contractual agreement itself may be, but License for use, especially in public forums is not, otherwise how can you come down so hard on someone like me for trying to abide by licensing agreement when those agreements are not know? You're saying on the one had I have to abide by Crosswire's agreement with the Copyright Owner and on the other hand I cannot know what those provisions are. I think if you check the contract, you'll see the actually license agreement as an Appendix or something of that sort for this very reason. The contracts are dictated by the publishers. When asked what they need to > say, we provide the broadest description of what they need to say at > minimum, but we don't ever suggest particular wording or terms. If the > terms are unacceptable to us, we communicate that clearly and let them > either amend their terms or withdraw the module. > Yes, true, however Crosswire as the licensee is not dealing with paper, but with digital forms of the text, so presumably as the licensee you've worked through some of the issues related to dealing with 'digial format'. At least your this recent business between Chris, Peter and I suggests that this is the case. Although the terms of Crosswire license to use of these Copyright works are not clear to me (dispite what Chris and Peter would have you believe) because I've seen no such terms, they are apparently clear to Chris and Peter. I have no trouble believing Chris and Peter have seen them, or they wouldn't be calling me to account. > We only need to prove our assertion with the publishers. Which we have do > on occasion. > Agreed. > > The wording of your request is inviting a "go pound sand" response. Please > be careful in how you word things. > > DM, I will be careful how I word things because such advice is always prudent advice. That said, I deny I was telling anyone to 'pound sand'. I am disappointed at the way my character, purpose, and contribution is contantly maligned in these discussions. It send the signal that 'new-comers' and their ideas are not welcome here dispite the claim this is an open community. This treatment on the part of some is not uniform by any means. However the method of dealing with conflict among Christian's is covered in the bible, and my disappointment stems from the idea that not all who engage in these disagreements make efforts to disagree on biblical principles. (I assume everyone here is a Christian). For example, I am particularly disappointed that I was accused of breaking Crosswire's licensing restrictions, yet no one has bothered to either publically name one module that was available at my repo that should have been, or provide access to Crosswire's license as evidence this was wrong. If Crosswire has legitimate license to distribution Copyright text and is going to use this license agreement like a hammer, it's not unrasonable to ask that it be made public, otherwise it has no right to defer to it in issues of disagreement. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 11:03:08 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 13:03:08 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: <1B71FC40-DA6A-482C-A05E-C1725F188642@crosswire.org> On Jan 7, 2013, at 12:58 PM, Andrew Thule wrote: > > > The wording of your request is inviting a "go pound sand" response. Please be careful in how you word things. > > DM, I will be careful how I word things because such advice is always prudent advice. > > That said, I deny I was telling anyone to 'pound sand'. I was suggesting that the use of "must" in your suggestion would prompt someone to tell you to "pound sand." In no way was I suggesting that you ever were telling someone else to do so. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 11:06:17 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:06:17 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: My experience with mirrors is that mirrors are done at the level of the Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the integrity and distribution of these things. That said, I think what you're saying is that you believe the Sword client needs some additional support to support mirrors, and I don't think that's entirely true. It may be that support for mirrors would be better accomplished through additional patches, but as it stands now I get all of Crosswire's modules as a proxy through either my public or private repo for the very simply reason it's safer for me to do so. I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a proxy), technically which means most clients (though perhaps not all) can manage this. So I'm speaking specifically about Bibletime, Xiphos, Alkitab, PocketSword, and Eloquent. If there are other clients out there, and Crosswire pursues 'mirrors', that decision will influence development. ~A On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: > Mirror management is a moot issue if the software doesn't support mirrors. > I have no plans to add such to JSword, unless it is added to SWORD first. I > highly doubt that it will be added to SWORD until a problem with resiliency > creates a real need. Even then, I'm not sure that that will be used as a > solution. > > In His Service, > DM > > On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: > > DM, I agree that not having thought through mirror management procedurally > (policy and best backpractice) is reason enough to hold off on such a > venture, but those problems are typically trivial to solve given effective > communication. > > Since technology is subordinat to intent, what needs to be worked out to > move forward along these lines is the clarification of intent. > > If I were to look back on this recent discussion, I'd suggest a number > of principles are already clear: > -CrossWire resevers the right to approve or deny mirrors > -CrossWire reserves the right to define which repositorories are > considered "root" repositories (so authoritive) > -Distribution of modules exclusively licensed to CrossWire should be > retained by Crosswire > -All Mirrors should take no longer than x (period of time) to accurately > reflect 'root repositories' > > Etc. > This issues have already (to some extent) been hashed through in debate, > however discussion on the matter was limited, unproductive and unclear > simply because of the degree of hostility the 'idea' of mirrors alone > produced. > > If there had been an attitude of 'open but undecided' reservation about > the matter, rather than outright 'hostility' its likely the issues you are > raising now could have been dealt with more readily. > > ~A > > > On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: > >> A few more reasons we discourage mirroring: >> SWORD and JSword have no means for managing mirrors. They expect each >> repository to be a unique collection of modules. >> >> A mirror that is partial, not containing all that is in the master >> repository, probably will be confusing to users. >> >> A mirror that is hosted along with questionable modules probably will >> give the appearance that CrossWire condones those modules. Especially when >> the modules are in the same repository. >> >> In Him, >> DM >> >> On Jan 4, 2013, at 9:09 AM, DM Smith wrote: >> >> From time to time, interest has been expressed in mirroring CrossWire's >> SWORD modules. I thought I'd reiterate our policy. >> >> We strongly, very strongly, discourage mirroring of the SWORD module >> repository. >> >> Those modules for which CrossWire has obtained distribution permission >> from copyright holders must not be mirrored. These have >> "DistributionLicense=Copyrighted; Permission to distribute granted to >> CrossWire" in their conf. CrossWire maintains correspondence for each of >> these modules. >> >> Mirrors are seldom current/correct, despite intentions. >> >> On occasion we have unintentionally hosted modules for which we did not >> have permission. When presented with an ownership claim, we typically will >> take the module offline immediately and validate the claim. If the claim is >> false, we will put the module back up. If the claim is true, we obtain >> permission before putting the module back online or we don't put it back. >> This is an important part of our stewardship. >> >> If or when CrossWire has problems with distribution, we'll tackle the >> problem at that time. Probably with a "Content Delivery Network" of >> CrossWire owned servers. >> >> This or some variation of this probably should be in the wiki. >> >> In His Service, >> DM >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 11:07:24 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:07:24 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: <1B71FC40-DA6A-482C-A05E-C1725F188642@crosswire.org> References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> <1B71FC40-DA6A-482C-A05E-C1725F188642@crosswire.org> Message-ID: Sorry, I misunderstood. I see what you're saying now. On Mon, Jan 7, 2013 at 1:03 PM, DM Smith wrote: > > On Jan 7, 2013, at 12:58 PM, Andrew Thule wrote: > > > >> >> The wording of your request is inviting a "go pound sand" response. >> Please be careful in how you word things. >> >> DM, I will be careful how I word things because such advice is always > prudent advice. > > That said, I deny I was telling anyone to 'pound sand'. > > > I was suggesting that the use of "must" in your suggestion would prompt > someone to tell you to "pound sand." In no way was I suggesting that you > ever were telling someone else to do so. > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 11:09:10 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:09:10 -0500 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> Message-ID: Except that the suggestion to support 'License Awareness' programatically I take to mean 'Sword Library", and the Sword Library need not be narrowly defined to suggest only Bible Programs can make use of the Library. ~A On Mon, Jan 7, 2013 at 12:47 PM, DM Smith wrote: > The CrossWire (SWORD/JSword based) "desktop" applications may download and > use any module provided by CrossWire. There is no need for these > applications to know or care what the license is. All modules are fair game. > > Applications that serve the web, such as SwordWEB and are not hosted on > the CrossWire server can only serve those modules to which they are legally > entitled to. It doesn't matter what the details of the license agreement > are with CrossWire, those organizations must obtain their own license > agreements. > > The need that STEP has for checking is that it can be used to serve the > WEB or be a desktop application. In the one case it cares; in the other, it > doesn't. So far we have left it to the user of the application to do the > right thing. > > In Him, > DM > > On Jan 7, 2013, at 12:31 PM, Andrew Thule wrote: > > I think this is a fanstastic idea, the idea of progamatically being able > to detect Status of a module programatically! Very good suggestion. > > On this example: > > "Say, a Xiphos user gets a module distributed by CrossWire, such as the > ESV. Does the Xiphos user then need to seek permission to use the module > through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need > to seek permission from Crossway? Possibly?" > > This is also a good example. > > Crossway as the Copyright Owner has granted CrossWire license to > distribute the text as a Sword modules, so the terms of this license > (permission) that govern how this works should be covered in a license > agreemnt (that defines things like 'Distribute', the scope of what > CrossWire means (develoepers or certain individuals) etc. > > So 'license to use' the ESV module has been set by the copyright owner, > but CrossWire should be able to clarify what that means programatically as > the licensee but also display the terms of the license (publicy) since > (presumably) it has already been worked out with Crossway and both parties > understand what it means. > > ~A > > > > > On Sun, Jan 6, 2013 at 5:59 PM, DM Smith wrote: > >> Yes. o.c.j.book.BookMetaData is the proper place for this. There are many >> of ways you can do it. There are several patterns in the class already. >> I'll leave the choice up to you. >> >> As Peter mentioned there are (at least) two questions that need to be >> answered: >> Redistributable? Are there modules that cannot be distributed at all. >> Commercial? Are there modules that preclude the use in a commercial >> context. (E.g. Ad driven). >> >> Note, when STEP is a desktop application or a web application, these >> might have different meanings. >> >> Here are details of how to dig it out today: >> >> o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE >> defines the list of acceptable values. >> >> You can access this via o.c.j.book.BookMetadata.getProperty as in: >> >> >> o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName()) >> >> You can then compare it to expected values as in "Copyrighted; Permission >> to distribute granted to CrossWire" >> >> Hope this helps. >> >> In Him, >> DM >> >> On Jan 6, 2013, at 12:05 PM, Chris Burrell wrote: >> >> > Hi >> > >> > Can I suggest adding something in the module configuration and/or >> sword/jsword backends that could indicate what kind of copyright we're >> dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. >> > >> > I personally would find that useful if I want to make available public >> domain resources in some fashion to others, and thereby not include some of >> the copyrighted material. >> > >> > For example, if I'm going to allow people to include hooks into STEP to >> obtain and display the Scriptures on their websites, I'd want to make sure >> I can sift through the texts that I make available and the ones that I >> don't (see my separate thread about CMSses) >> > >> > I guess this could be as trivial as looking for "Public domain" or >> "Copyright" in the field in the configuration, but in the numerous emails >> from the last few days, someone said something along the lines that we were >> trying to be consistent but aren't always. >> > >> > If, we think, this is consistent enough, I'd be happy to implement a >> simple getter on the BookMetadata object in JSword. >> > >> > If we don't think this is valuable and the .conf files aren't >> consistent, I'll simply maintain an "opt-in" list for those resources that >> are public domain + those I've obtained permissions from >> > Chris >> > >> > _______________________________________________ >> > sword-devel mailing list: sword-devel at crosswire.org >> > http://www.crosswire.org/mailman/listinfo/sword-devel >> > Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Mon Jan 7 11:09:31 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 7 Jan 2013 12:09:31 -0600 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: On Mon, Jan 7, 2013 at 11:58 AM, Andrew Thule wrote: > > On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: > >> No, we cannot publish the terms of licensing agreements. Think about it. >> These are confidential, privileged contracts between organizations. > > > Umm, with software Licenses, Acceptable Use Policies, Copyright Restrictions > and Copyright limitations are not typically priviledge .. > > The contractual agreement itself may be, but License for use, especially in > public forums is not, otherwise how can you come down so hard on someone > like me for trying to abide by licensing agreement when those agreements are > not know? > > You're saying on the one had I have to abide by Crosswire's agreement with > the Copyright Owner and on the other hand I cannot know what those > provisions are. False. We're saying you have to abide by Copyright laws. According to Copyright laws you have no claim on these modules unless there is either (1) no Copyright holder, as is the case for any modules in the public domain or (2) you have been granted permission by the Copyright holder. This could be in the case of content where the holder has publicly permitted anyone rights, otherwise you need to negotiate your own license with the Copyright holder if you want to distribute. You have no need to make your license public to anyone if you negotiate the rights to a module and neither does CrossWire. The only people who need to know the specific terms are CrossWire's point of contact (usually Troy or Chris but it could be whoever negotiated the contract) and the Copyright holder. Additionally a copy could be submitted to law enforcement or courts if legislation arose or the like. > For example, I am particularly disappointed that I was accused of breaking > Crosswire's licensing restrictions, yet no one has bothered to either > publically name one module that was available at my repo that should have > been, or provide access to Crosswire's license as evidence this was wrong. You don't need to see the specifics of CrossWire's license agreements. You just need to understand basic Copyright function. Is the text under Copyright? Do you have the permission of the Copyright holder to distribute the text? If the answer to the first question is "yes" and the answer to the second is "no" then you don't have the right to distribute the work. Regardless of who DOES have the right, you do not. And regardless of under which conditions they have the right, you do not. You don't need to know under what permissions CrossWire has the right to distribute a module publicly in electronic format anymore than you need to know what agreement Zondervan has to publish a paper copy. You also don't need to know what agreement Amazon has or Netflix has to electronically make available copies of movies to know that you do not have a right to mirror their content without permission from at least the Copyright holder. --Greg From thulester at gmail.com Mon Jan 7 11:19:21 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:19:21 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <50E9C213.5060301@cox.net> References: <50E9C213.5060301@cox.net> Message-ID: DM, all of which you said is reasonable; no issues from me. My point was in the efforts to assist with module develoment, I apparently crossed some line. I offered to send an OSIS update, and made a testing version of it available. The debate started (as you note) because of my making a testing version available (this taken to be 'distribution') I don't have a hard time believing Crosswire has worked out the details of its licensing agreemnt to distribute the Copyright holder's text in through a very sensitive process (or even that these agreements come with residual sensitivies), even if I find it difficult to believe distribution of (complied) modules for the sake of development is expressly excluded or limited in otherways. What I did have a hard time with was being publicly held accountable to license restrictions reasonably unknown to me (and apparently secret), while having the issue made personal. It isn't reasonable to assume I knew sharing a compiled module with this group would set off a firestorm if the license between the ISV foundation and CrossWire is treated as confidential .. Jerry, well I appreicate what you're saying, I suspect these issues are issues Crosswire needs to give more thought to internally so that module developers (volunteers, newcomers etc) are not expected to either provide the solution or get caught in the crossfire when a can-o-worms gets opened. ~A On Sun, Jan 6, 2013 at 1:27 PM, jhphx wrote: > On 1/6/2013 1:54 AM, Andrew Thule wrote: > >> I'm currently reviewing its contents to ensure no module exclusive to >> Crosswire was available. I will be putting it back up on completion of my >> review. >> ... >> > > I am not sure how you think being exclusive to Crosswire works in this > context, but, > > IF: > a) none of those other sources have legitimate (licensed) copies of a > copyrighted text or it's derivatives, > OR > b) none of those sources provided you with a legitimate license to do > whatever you do, > OR > c) it simply appears like you are violating anyone's copyrights, > THEN: > It won't matter to CrossWire how many other sources there are, you > would appear to be, and in fact could be, a threat to CrossWire's ability > to distribute if it appears that CrossWire is condoning what you do. It > does not matter how the other sources see it, or how you see it, it matters > how it seems to CrossWire and how it may seem to the publishers they work > with. > > Andrew, you appear to want to help. There are many things someone like you > could do, but maybe working on copyrighted modules and distribution of them > is not the right task for now. There remains many other things needing to > be done. > > If you still feel the need to work on a copyrighted text for CrossWire > then I suggest you ask yourself three things: > a) could this work produce a copy, new copy, new version, or derivative of > the text, > b) could this work result in exposing, intentionally or not, a copy so > that wild (any unlicensed) distribution could result, > c) could this work possibly offend CrossWire or the publishers they work > with. > > If the answer to any of those is yes then ask if you should work on it and > exactly how you should do it to avoid these problems. Although, at this > time "just ask" may be the best policy. > > Just a suggestion, I am not an official voice on these matters. > > Jerry > > > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Mon Jan 7 11:19:29 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Mon, 7 Jan 2013 18:19:29 +0000 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: I think we've got the answers across multiple threads. DM answers your question in my thread. others in other threads. 1. All modules are fair game for sword front ends to use and display. 2. Modifying modules and/or redistributing is not allowed for modules marked as Copyrighted permission granted CrossWire 3. Conf files are occasionally inconsistent in the copyright field and therefore setting up mirrors is strongly discouraged as mirror owners may well end up hosting modules illegally. This threatens the ongoing relationship between CrossWire and the publishers. 4. Modifying modules in general is discouraged as a lonesome task as there are often tools used to generate these modules and therfore the source may not be available to the keen module editor. There may also be extra restrictions on this modules which restrict the type of modifications, e.g. adding strong numbers 5. As a result of 4, everyone is encouraged to contact Chris L to find out who the 'owner' of a module is before making any modifications but will then be encouraged to participate is circumstances allow. 6. Sword and JSword so not cope well with repositories hosting the same module. This is a further reason for discouraging the instalation of Mirrors for public use. Hope that is a good summary of the discussion so far. Chris On 7 Jan 2013 17:59, "Andrew Thule" wrote: > > On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: > > No, we cannot publish the terms of licensing agreements. Think about it. >> These are confidential, privileged contracts between organizations. >> > > Umm, with software Licenses, Acceptable Use Policies, Copyright > Restrictions and Copyright limitations are not typically priviledge .. > > The contractual agreement itself may be, but License for use, especially > in public forums is not, otherwise how can you come down so hard on someone > like me for trying to abide by licensing agreement when those agreements > are not know? > > You're saying on the one had I have to abide by Crosswire's agreement with > the Copyright Owner and on the other hand I cannot know what those > provisions are. > > I think if you check the contract, you'll see the actually license > agreement as an Appendix or something of that sort for this very reason. > > > The contracts are dictated by the publishers. When asked what they need to >> say, we provide the broadest description of what they need to say at >> minimum, but we don't ever suggest particular wording or terms. If the >> terms are unacceptable to us, we communicate that clearly and let them >> either amend their terms or withdraw the module. >> > Yes, true, however Crosswire as the licensee is not dealing with paper, > but with digital forms of the text, so presumably as the licensee you've > worked through some of the issues related to dealing with 'digial format'. > At least your this recent business between Chris, Peter and I suggests that > this is the case. > > Although the terms of Crosswire license to use of these Copyright > works are not clear to me (dispite what Chris and Peter would have you > believe) because I've seen no such terms, they are apparently clear > to Chris and Peter. I have no trouble believing Chris and Peter have seen > them, or they wouldn't be calling me to account. > > > >> We only need to prove our assertion with the publishers. Which we have do >> on occasion. >> > Agreed. > > >> >> The wording of your request is inviting a "go pound sand" response. >> Please be careful in how you word things. >> >> DM, I will be careful how I word things because such advice is always > prudent advice. > > That said, I deny I was telling anyone to 'pound sand'. I am disappointed > at the way my character, purpose, and contribution is contantly maligned in > these discussions. It send the signal that 'new-comers' and their ideas > are not welcome here dispite the claim this is an open community. This > treatment on the part of some is not uniform by any means. > > However the method of dealing with conflict among Christian's is covered > in the bible, and my disappointment stems from the idea that not all who > engage in these disagreements make efforts to disagree on biblical > principles. (I assume everyone here is a Christian). > > For example, I am particularly disappointed that I was accused of breaking > Crosswire's licensing restrictions, yet no one has bothered to either > publically name one module that was available at my repo that should have > been, or provide access to Crosswire's license as evidence this was wrong. > > If Crosswire has legitimate license to distribution Copyright text and is > going to use this license agreement like a hammer, it's not unrasonable to > ask that it be made public, otherwise it has no right to defer to it in > issues of disagreement. > ~A > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Mon Jan 7 11:26:13 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Mon, 7 Jan 2013 18:26:13 +0000 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> Message-ID: Coming back to my original point. Is there appetite for such support in the sword modules? Peter sends to suggest 'Maybe'. DM seems to suggest 'No'. I'm happy to make my enhancements in the STEP code if nobody wants this. Chris Chris On 7 Jan 2013 18:10, "Andrew Thule" wrote: > Except that the suggestion to support 'License Awareness' programatically > I take to mean 'Sword Library", and the Sword Library need not be narrowly > defined to suggest only Bible Programs can make use of the Library. > > ~A > > > On Mon, Jan 7, 2013 at 12:47 PM, DM Smith wrote: > >> The CrossWire (SWORD/JSword based) "desktop" applications may download >> and use any module provided by CrossWire. There is no need for these >> applications to know or care what the license is. All modules are fair game. >> >> Applications that serve the web, such as SwordWEB and are not hosted on >> the CrossWire server can only serve those modules to which they are legally >> entitled to. It doesn't matter what the details of the license agreement >> are with CrossWire, those organizations must obtain their own license >> agreements. >> >> The need that STEP has for checking is that it can be used to serve the >> WEB or be a desktop application. In the one case it cares; in the other, it >> doesn't. So far we have left it to the user of the application to do the >> right thing. >> >> In Him, >> DM >> >> On Jan 7, 2013, at 12:31 PM, Andrew Thule wrote: >> >> I think this is a fanstastic idea, the idea of progamatically being able >> to detect Status of a module programatically! Very good suggestion. >> >> On this example: >> >> "Say, a Xiphos user gets a module distributed by CrossWire, such as the >> ESV. Does the Xiphos user then need to seek permission to use the module >> through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need >> to seek permission from Crossway? Possibly?" >> >> This is also a good example. >> >> Crossway as the Copyright Owner has granted CrossWire license to >> distribute the text as a Sword modules, so the terms of this license >> (permission) that govern how this works should be covered in a license >> agreemnt (that defines things like 'Distribute', the scope of what >> CrossWire means (develoepers or certain individuals) etc. >> >> So 'license to use' the ESV module has been set by the copyright owner, >> but CrossWire should be able to clarify what that means programatically as >> the licensee but also display the terms of the license (publicy) since >> (presumably) it has already been worked out with Crossway and both parties >> understand what it means. >> >> ~A >> >> >> >> >> On Sun, Jan 6, 2013 at 5:59 PM, DM Smith wrote: >> >>> Yes. o.c.j.book.BookMetaData is the proper place for this. There are >>> many of ways you can do it. There are several patterns in the class >>> already. I'll leave the choice up to you. >>> >>> As Peter mentioned there are (at least) two questions that need to be >>> answered: >>> Redistributable? Are there modules that cannot be distributed at all. >>> Commercial? Are there modules that preclude the use in a commercial >>> context. (E.g. Ad driven). >>> >>> Note, when STEP is a desktop application or a web application, these >>> might have different meanings. >>> >>> Here are details of how to dig it out today: >>> >>> o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE >>> defines the list of acceptable values. >>> >>> You can access this via o.c.j.book.BookMetadata.getProperty as in: >>> >>> >>> o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName()) >>> >>> You can then compare it to expected values as in "Copyrighted; >>> Permission to distribute granted to CrossWire" >>> >>> Hope this helps. >>> >>> In Him, >>> DM >>> >>> On Jan 6, 2013, at 12:05 PM, Chris Burrell wrote: >>> >>> > Hi >>> > >>> > Can I suggest adding something in the module configuration and/or >>> sword/jsword backends that could indicate what kind of copyright we're >>> dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc. >>> > >>> > I personally would find that useful if I want to make available public >>> domain resources in some fashion to others, and thereby not include some of >>> the copyrighted material. >>> > >>> > For example, if I'm going to allow people to include hooks into STEP >>> to obtain and display the Scriptures on their websites, I'd want to make >>> sure I can sift through the texts that I make available and the ones that I >>> don't (see my separate thread about CMSses) >>> > >>> > I guess this could be as trivial as looking for "Public domain" or >>> "Copyright" in the field in the configuration, but in the numerous emails >>> from the last few days, someone said something along the lines that we were >>> trying to be consistent but aren't always. >>> > >>> > If, we think, this is consistent enough, I'd be happy to implement a >>> simple getter on the BookMetadata object in JSword. >>> > >>> > If we don't think this is valuable and the .conf files aren't >>> consistent, I'll simply maintain an "opt-in" list for those resources that >>> are public domain + those I've obtained permissions from >>> > Chris >>> > >>> > _______________________________________________ >>> > sword-devel mailing list: sword-devel at crosswire.org >>> > http://www.crosswire.org/mailman/listinfo/sword-devel >>> > Instructions to unsubscribe/change your settings at above page >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Mon Jan 7 11:26:31 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 7 Jan 2013 12:26:31 -0600 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule wrote: > What I did have a hard time with was being publicly held accountable to > license restrictions reasonably unknown to me (and apparently secret), while > having the issue made personal. It isn't reasonable to assume I knew > sharing a compiled module with this group would set off a firestorm if the > license between the ISV foundation and CrossWire is treated as confidential You're not being held accountable to CrossWire's terms of distribution. You're being held accountable to Copyright law. Something you are reasonably expected to know. But which you have repeatedly shown yourself either unknowledgeable of - in the case of the Dead Sea Scroll modules discussion - or unwilling to abide by without some sort of extra treatment - in this case knowledge of a contract between two parties which has no bearing on you. Stop trying to insult the rest of our intelligences by taking the position of victim in this. You have shown flagrant disregard for Copyright and an unwilling attitude to learn or be instructed in it. --Greg From thulester at gmail.com Mon Jan 7 11:33:01 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:33:01 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: Umm, Greg, you realise that under Copyright Law Crosswire has no right to Copy right text either (at least not without license) or to void its own license agreement? If Crosswire is licensed to distribute Copyright text for which it is not the owner: The Copyright Owner must establish the terms of the licensing with Crosswire. If Crossire then publicaly re-distributes the text under license, CrossWire has a legal obligation under Copyright law, to uphold the owners orginal license which means it can't keep the license agreement 'secret', otherwise the constraints and allowances established in the original license are being stopped at Crosswire. Sorry, but Crosswire has an obligation (under Copyright law) as distributor to share with its users the terms of each Copyright owner's license. If Crosswire has the right distribute a module publically, than it can prove it has this right by producing a licensing agreement since such an agreement is how the orginal Copyright owner granted this right in the first place. Producing such an agreement also conveys to users of CrossWire users their obligations inherited through their use of CrossWire's module (since what restrictions allowances applied to CrossWire, also apply to users). ~A On Mon, Jan 7, 2013 at 1:09 PM, Greg Hellings wrote: > On Mon, Jan 7, 2013 at 11:58 AM, Andrew Thule wrote: > > > > On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: > > > >> No, we cannot publish the terms of licensing agreements. Think about it. > >> These are confidential, privileged contracts between organizations. > > > > > > Umm, with software Licenses, Acceptable Use Policies, Copyright > Restrictions > > and Copyright limitations are not typically priviledge .. > > > > The contractual agreement itself may be, but License for use, especially > in > > public forums is not, otherwise how can you come down so hard on someone > > like me for trying to abide by licensing agreement when those agreements > are > > not know? > > > > You're saying on the one had I have to abide by Crosswire's agreement > with > > the Copyright Owner and on the other hand I cannot know what those > > provisions are. > > False. We're saying you have to abide by Copyright laws. According to > Copyright laws you have no claim on these modules unless there is > either (1) no Copyright holder, as is the case for any modules in the > public domain or (2) you have been granted permission by the Copyright > holder. This could be in the case of content where the holder has > publicly permitted anyone rights, otherwise you need to negotiate your > own license with the Copyright holder if you want to distribute. You > have no need to make your license public to anyone if you negotiate > the rights to a module and neither does CrossWire. The only people who > need to know the specific terms are CrossWire's point of contact > (usually Troy or Chris but it could be whoever negotiated the > contract) and the Copyright holder. Additionally a copy could be > submitted to law enforcement or courts if legislation arose or the > like. > > > For example, I am particularly disappointed that I was accused of > breaking > > Crosswire's licensing restrictions, yet no one has bothered to either > > publically name one module that was available at my repo that should have > > been, or provide access to Crosswire's license as evidence this was > wrong. > > You don't need to see the specifics of CrossWire's license agreements. > You just need to understand basic Copyright function. Is the text > under Copyright? Do you have the permission of the Copyright holder to > distribute the text? If the answer to the first question is "yes" and > the answer to the second is "no" then you don't have the right to > distribute the work. Regardless of who DOES have the right, you do > not. And regardless of under which conditions they have the right, you > do not. > > You don't need to know under what permissions CrossWire has the right > to distribute a module publicly in electronic format anymore than you > need to know what agreement Zondervan has to publish a paper copy. You > also don't need to know what agreement Amazon has or Netflix has to > electronically make available copies of movies to know that you do not > have a right to mirror their content without permission from at least > the Copyright holder. > > --Greg > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Mon Jan 7 11:37:43 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Mon, 07 Jan 2013 19:37:43 +0100 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> Message-ID: <20130107183743.86840@gmx.net> > Von: Chris Burrell > > Is there appetite for such support in the sword modules? I do think there is value in this for supporting a Web API. You could host any number of modules with many different licenses and many different API users could have a reasonably automatic way of using the offered texts without doing any sifting by hand for texts allowable for their specific purposes. I am not sure if it makes sense anywhere else. Peter From thulester at gmail.com Mon Jan 7 11:43:18 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:43:18 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: Greg, its not clear you understand copyright law. Copyright Law is generic .. it applies generally. If you read American, Canadian, or European copyright law you won't find anything mentionion CrossWire, ISV, ESV specifically. That means it lays down principles. Therefore, copyright law with respect to either printed work or digital work covers specifics in licenses. If you read the licensing that comes with the ESV (found here http://www.esv.org/tools/licensing/ ) which is specific, you'll see that nothing there says anything about CrossWire having the right to distribute the ESV either, which means CrossWire's 'right' to distribute the ESV (since the entire bible is being distributed) is covered under its own license. Thefore anyone using CrossWire's ESV module, or developing that module are bound by a license that is apparently 'confidential'. Therefore if I have done as I've claimed, and distributed the ISV in contravention of some law, you should be able to produce some document that says I'm not permitted to do it. Since the Copyright act doesn't specifically speak about the ISV, you would presumably go to the ISV foundation site. Yes there is a document there (just like with the ESV), except it says nothing about CrossWire's right to distribute, so that license is not the one I've breached. For Crosswire to assert its right to distribute the ISV it must have a license that says this, and that is what we're talking about. ~A . On Mon, Jan 7, 2013 at 1:26 PM, Greg Hellings wrote: > On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule wrote: > > What I did have a hard time with was being publicly held accountable to > > license restrictions reasonably unknown to me (and apparently secret), > while > > having the issue made personal. It isn't reasonable to assume I knew > > sharing a compiled module with this group would set off a firestorm if > the > > license between the ISV foundation and CrossWire is treated as > confidential > > You're not being held accountable to CrossWire's terms of > distribution. You're being held accountable to Copyright law. > Something you are reasonably expected to know. But which you have > repeatedly shown yourself either unknowledgeable of - in the case of > the Dead Sea Scroll modules discussion - or unwilling to abide by > without some sort of extra treatment - in this case knowledge of a > contract between two parties which has no bearing on you. > > Stop trying to insult the rest of our intelligences by taking the > position of victim in this. You have shown flagrant disregard for > Copyright and an unwilling attitude to learn or be instructed in it. > > --Greg > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 11:44:17 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 13:44:17 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: On Jan 7, 2013, at 12:58 PM, Andrew Thule wrote: > > On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: > > No, we cannot publish the terms of licensing agreements. Think about it. These are confidential, privileged contracts between organizations. > > Umm, with software Licenses, Acceptable Use Policies, Copyright Restrictions and Copyright limitations are not typically priviledge .. Each copyright owner has several fields in the conf that they can fill out with that information. Most use the About field. A few use some other fields. Consult the module's conf for the information that you want. If it is not there then please assume that the owner did not want to share it or did not provide it. > > The contractual agreement itself may be, but License for use, especially in public forums is not, otherwise how can you come down so hard on someone like me for trying to abide by licensing agreement when those agreements are not know? > > You're saying on the one had I have to abide by Crosswire's agreement with the Copyright Owner and on the other hand I cannot know what those provisions are. > > I think if you check the contract, you'll see the actually license agreement as an Appendix or something of that sort for this very reason. Have I come down hard on you? I know I have been direct and have tried to be informative. We've only been talking about one part of the license agreement: the right to re-distribute modules. We think that the DistributionLicense field states it very well. > > > The contracts are dictated by the publishers. When asked what they need to say, we provide the broadest description of what they need to say at minimum, but we don't ever suggest particular wording or terms. If the terms are unacceptable to us, we communicate that clearly and let them either amend their terms or withdraw the module. > Yes, true, however Crosswire as the licensee is not dealing with paper, but with digital forms of the text, so presumably as the licensee you've worked through some of the issues related to dealing with 'digial format'. At least your this recent business between Chris, Peter and I suggests that this is the case. > > Although the terms of Crosswire license to use of these Copyright works are not clear to me (dispite what Chris and Peter would have you believe) because I've seen no such terms, they are apparently clear to Chris and Peter. I have no trouble believing Chris and Peter have seen them, or they wouldn't be calling me to account. I don't think that is the case. I work on copyright modules and have never seen a license agreement. I've never felt the need to see it. I always treat a copyrighted work as a confidential, intellectual property to which I only have sufficient privileges to do my work on the module. I'm sure that I might be going beyond what is required, but I'd rather make that mistake than betraying the owner's trust. Peter and Chris will have seen those agreements that they have participated in obtaining. They have no need to have seen any others. > > > We only need to prove our assertion with the publishers. Which we have do on occasion. > Agreed. > > > The wording of your request is inviting a "go pound sand" response. Please be careful in how you word things. > > DM, I will be careful how I word things because such advice is always prudent advice. > > That said, I deny I was telling anyone to 'pound sand'. I am disappointed at the way my character, purpose, and contribution is contantly maligned in these discussions. It send the signal that 'new-comers' and their ideas are not welcome here dispite the claim this is an open community. This treatment on the part of some is not uniform by any means. > > However the method of dealing with conflict among Christian's is covered in the bible, and my disappointment stems from the idea that not all who engage in these disagreements make efforts to disagree on biblical principles. (I assume everyone here is a Christian). > > For example, I am particularly disappointed that I was accused of breaking Crosswire's licensing restrictions, yet no one has bothered to either publically name one module that was available at my repo that should have been, or provide access to Crosswire's license as evidence this was wrong. Peter has told you privately of at least one that he was able to download. Do you want that to be repeated here? > > If Crosswire has legitimate license to distribution Copyright text and is going to use this license agreement like a hammer, it's not unrasonable to ask that it be made public, otherwise it has no right to defer to it in issues of disagreement. We accurately summarize it in the conf. We have explained it here. What is hard about understanding that? What more is needed? In His Service, DM -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Mon Jan 7 11:46:51 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Mon, 07 Jan 2013 19:46:51 +0100 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: <20130107184651.86820@gmx.net> > Von: Andrew Thule > Sorry, but Crosswire has an obligation (under Copyright law) as > distributor > to share with its users the terms of each Copyright owner's license. It does. As per module conf entry re DistributionLicense. It tells you everything you must know. If you look at it, think it does not answer your question re onwards distribution, then chances are the answer is no. Unless you have your own permissions or you make fair use. Peter From dmsmith at crosswire.org Mon Jan 7 11:52:52 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 13:52:52 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: Message-ID: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> I guess I need more information on mirrors. Let's say that there are to mirrors X and Y. For what ever reason, X has A, B, C, D and Y has A, D, E. Software is configured to use Y. When it goes to get a list of files, what does it get? If it requests B, what does it get? Same questions for software configured for X and request for E. -- DM On Jan 7, 2013, at 1:06 PM, Andrew Thule wrote: > My experience with mirrors is that mirrors are done at the level of the Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the integrity and distribution of these things. > > That said, I think what you're saying is that you believe the Sword client needs some additional support to support mirrors, and I don't think that's entirely true. It may be that support for mirrors would be better accomplished through additional patches, but as it stands now I get all of Crosswire's modules as a proxy through either my public or private repo for the very simply reason it's safer for me to do so. > > I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a proxy), technically which means most clients (though perhaps not all) can manage this. > > So I'm speaking specifically about Bibletime, Xiphos, Alkitab, PocketSword, and Eloquent. If there are other clients out there, and Crosswire pursues 'mirrors', that decision will influence development. > > ~A > > > On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: > Mirror management is a moot issue if the software doesn't support mirrors. I have no plans to add such to JSword, unless it is added to SWORD first. I highly doubt that it will be added to SWORD until a problem with resiliency creates a real need. Even then, I'm not sure that that will be used as a solution. > > In His Service, > DM > > On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: > >> DM, I agree that not having thought through mirror management procedurally (policy and best backpractice) is reason enough to hold off on such a venture, but those problems are typically trivial to solve given effective communication. >> >> Since technology is subordinat to intent, what needs to be worked out to move forward along these lines is the clarification of intent. >> >> If I were to look back on this recent discussion, I'd suggest a number of principles are already clear: >> -CrossWire resevers the right to approve or deny mirrors >> -CrossWire reserves the right to define which repositorories are considered "root" repositories (so authoritive) >> -Distribution of modules exclusively licensed to CrossWire should be retained by Crosswire >> -All Mirrors should take no longer than x (period of time) to accurately reflect 'root repositories' >> >> Etc. >> This issues have already (to some extent) been hashed through in debate, however discussion on the matter was limited, unproductive and unclear simply because of the degree of hostility the 'idea' of mirrors alone produced. >> >> If there had been an attitude of 'open but undecided' reservation about the matter, rather than outright 'hostility' its likely the issues you are raising now could have been dealt with more readily. >> >> ~A >> >> >> On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: >> A few more reasons we discourage mirroring: >> SWORD and JSword have no means for managing mirrors. They expect each repository to be a unique collection of modules. >> >> A mirror that is partial, not containing all that is in the master repository, probably will be confusing to users. >> >> A mirror that is hosted along with questionable modules probably will give the appearance that CrossWire condones those modules. Especially when the modules are in the same repository. >> >> In Him, >> DM >> >> On Jan 4, 2013, at 9:09 AM, DM Smith wrote: >> >>> From time to time, interest has been expressed in mirroring CrossWire's SWORD modules. I thought I'd reiterate our policy. >>> >>> We strongly, very strongly, discourage mirroring of the SWORD module repository. >>> >>> Those modules for which CrossWire has obtained distribution permission from copyright holders must not be mirrored. These have "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire" in their conf. CrossWire maintains correspondence for each of these modules. >>> >>> Mirrors are seldom current/correct, despite intentions. >>> >>> On occasion we have unintentionally hosted modules for which we did not have permission. When presented with an ownership claim, we typically will take the module offline immediately and validate the claim. If the claim is false, we will put the module back up. If the claim is true, we obtain permission before putting the module back online or we don't put it back. This is an important part of our stewardship. >>> >>> If or when CrossWire has problems with distribution, we'll tackle the problem at that time. Probably with a "Content Delivery Network" of CrossWire owned servers. >>> >>> This or some variation of this probably should be in the wiki. >>> >>> In His Service, >>> DM >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 11:53:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 13:53:03 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: Chris this list in an of itself is not sufficient (legally) to establish these principles. It is the Copyright owners who make this determination, not Crosswire list members. Each Copyright owner is entitled to impose unique restrictions on the use of their texts. CrossWire is bound on a module by module basis to abide by the license agreement agreed to by the Copyright owner. (Although these agreements may be smiliar, I doubt very much they are exactly the same. You can see from comparing ESV's general license to ISVs general license (found under legal) they differ. It may be the case that the ISV foundations license to Crosswire is not as restritive as Peter and Chris claimed and my action of sharing a compile module on a separate server didn't in fact breach anything. Only by inspecting Crosswire's license obligations can this be determined though. Now that I've been tarred and feathered, I would kind of like to know if Crosswires license to distrbiute the ISV indeed prohibits this (so I can know if I'm guilty as charged or not). Also, if no such restriction exists, Peter's claim that I have no right to distribute the ISV doesn't hold, and I'll consider continuing to server it on my repo. ~A On Mon, Jan 7, 2013 at 1:19 PM, Chris Burrell wrote: > I think we've got the answers across multiple threads. DM answers your > question in my thread. others in other threads. > > 1. All modules are fair game for sword front ends to use and display. > > 2. Modifying modules and/or redistributing is not allowed for modules > marked as Copyrighted permission granted CrossWire > > 3. Conf files are occasionally inconsistent in the copyright field and > therefore setting up mirrors is strongly discouraged as mirror owners may > well end up hosting modules illegally. This threatens the ongoing > relationship between CrossWire and the publishers. > > 4. Modifying modules in general is discouraged as a lonesome task as there > are often tools used to generate these modules and therfore the source may > not be available to the keen module editor. There may also be extra > restrictions on this modules which restrict the type of modifications, e.g. > adding strong numbers > > 5. As a result of 4, everyone is encouraged to contact Chris L to find out > who the 'owner' of a module is before making any modifications but will > then be encouraged to participate is circumstances allow. > > 6. Sword and JSword so not cope well with repositories hosting the same > module. This is a further reason for discouraging the instalation of > Mirrors for public use. > > Hope that is a good summary of the discussion so far. > > Chris > On 7 Jan 2013 17:59, "Andrew Thule" wrote: > >> >> On Sun, Jan 6, 2013 at 11:12 AM, DM Smith wrote: >> >> No, we cannot publish the terms of licensing agreements. Think about it. >>> These are confidential, privileged contracts between organizations. >>> >> >> Umm, with software Licenses, Acceptable Use Policies, Copyright >> Restrictions and Copyright limitations are not typically priviledge .. >> >> The contractual agreement itself may be, but License for use, especially >> in public forums is not, otherwise how can you come down so hard on someone >> like me for trying to abide by licensing agreement when those agreements >> are not know? >> >> You're saying on the one had I have to abide by Crosswire's agreement >> with the Copyright Owner and on the other hand I cannot know what those >> provisions are. >> >> I think if you check the contract, you'll see the actually license >> agreement as an Appendix or something of that sort for this very reason. >> >> >> The contracts are dictated by the publishers. When asked what they need >>> to say, we provide the broadest description of what they need to say at >>> minimum, but we don't ever suggest particular wording or terms. If the >>> terms are unacceptable to us, we communicate that clearly and let them >>> either amend their terms or withdraw the module. >>> >> Yes, true, however Crosswire as the licensee is not dealing with paper, >> but with digital forms of the text, so presumably as the licensee you've >> worked through some of the issues related to dealing with 'digial format'. >> At least your this recent business between Chris, Peter and I suggests that >> this is the case. >> >> Although the terms of Crosswire license to use of these Copyright >> works are not clear to me (dispite what Chris and Peter would have you >> believe) because I've seen no such terms, they are apparently clear >> to Chris and Peter. I have no trouble believing Chris and Peter have seen >> them, or they wouldn't be calling me to account. >> >> >> >>> We only need to prove our assertion with the publishers. Which we have >>> do on occasion. >>> >> Agreed. >> >> >>> >>> The wording of your request is inviting a "go pound sand" response. >>> Please be careful in how you word things. >>> >>> DM, I will be careful how I word things because such advice is always >> prudent advice. >> >> That said, I deny I was telling anyone to 'pound sand'. I am >> disappointed at the way my character, purpose, and contribution is >> contantly maligned in these discussions. It send the signal that >> 'new-comers' and their ideas are not welcome here dispite the claim this is >> an open community. This treatment on the part of some is not uniform by any >> means. >> >> However the method of dealing with conflict among Christian's is covered >> in the bible, and my disappointment stems from the idea that not all who >> engage in these disagreements make efforts to disagree on biblical >> principles. (I assume everyone here is a Christian). >> >> For example, I am particularly disappointed that I was accused of >> breaking Crosswire's licensing restrictions, yet no one has bothered to >> either publically name one module that was available at my repo that should >> have been, or provide access to Crosswire's license as evidence this was >> wrong. >> >> If Crosswire has legitimate license to distribution Copyright text and is >> going to use this license agreement like a hammer, it's not unrasonable to >> ask that it be made public, otherwise it has no right to defer to it in >> issues of disagreement. >> ~A >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Mon Jan 7 12:02:42 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 7 Jan 2013 13:02:42 -0600 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: On Mon, Jan 7, 2013 at 12:43 PM, Andrew Thule wrote: > Greg, its not clear you understand copyright law. > > Copyright Law is generic .. it applies generally. If you read American, > Canadian, or European copyright law you won't find anything mentionion > CrossWire, ISV, ESV specifically. That means it lays down principles. > > Therefore, copyright law with respect to either printed work or digital work > covers specifics in licenses. If you read the licensing that comes with the > ESV (found here http://www.esv.org/tools/licensing/ ) which is specific, > you'll see that nothing there says anything about CrossWire having the right > to distribute the ESV either, which means CrossWire's 'right' to distribute > the ESV (since the entire bible is being distributed) is covered under its > own license. > > Thefore anyone using CrossWire's ESV module, or developing that module are > bound by a license that is apparently 'confidential'. > > Therefore if I have done as I've claimed, and distributed the ISV in > contravention of some law, you should be able to produce some document that > says I'm not permitted to do it. Since the Copyright act doesn't > specifically speak about the ISV, you would presumably go to the ISV > foundation site. Yes there is a document there (just like with the ESV), > except it says nothing about CrossWire's right to distribute, so that > license is not the one I've breached. For Crosswire to assert its right to > distribute the ISV it must have a license that says this, and that is what > we're talking about. The text is Copyrighted. CrossWire informs you of this in the conf file. You are bound by whatever rights have been granted to you by the holder of the ISV's Copyright. In this case, the text on the page you reference is the ISV's generic rights that go out to anyone who legally holds a copy of the text. You legally hold a copy of the text. Therefore you are bound by that statement by the ISV's Copyright holder. The rights that CrossWire has negotiated separately have no bearing on your rights to use or distribute the text. Those rights apply to CrossWire. You have no need to see the agreements because they in no way have a bearing on you. You are neither CrossWire nor the publisher of the ISV nor any legal or law enforcement organization within whose jurisdiction any of the affected parties fall. That is how Copyright law works in the USA which is where CrossWire falls. If you can point to a jurisdiction where you reside that is affected by a law or requirement that Copyright agreements be made public then you might have grounds for your request. Until then, you are asking for private information which does not concern you. --Greg > > ~A > . > > > On Mon, Jan 7, 2013 at 1:26 PM, Greg Hellings > wrote: >> >> On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule wrote: >> > What I did have a hard time with was being publicly held accountable to >> > license restrictions reasonably unknown to me (and apparently secret), >> > while >> > having the issue made personal. It isn't reasonable to assume I knew >> > sharing a compiled module with this group would set off a firestorm if >> > the >> > license between the ISV foundation and CrossWire is treated as >> > confidential >> >> You're not being held accountable to CrossWire's terms of >> distribution. You're being held accountable to Copyright law. >> Something you are reasonably expected to know. But which you have >> repeatedly shown yourself either unknowledgeable of - in the case of >> the Dead Sea Scroll modules discussion - or unwilling to abide by >> without some sort of extra treatment - in this case knowledge of a >> contract between two parties which has no bearing on you. >> >> Stop trying to insult the rest of our intelligences by taking the >> position of victim in this. You have shown flagrant disregard for >> Copyright and an unwilling attitude to learn or be instructed in it. >> >> --Greg >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From thulester at gmail.com Mon Jan 7 12:04:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 14:04:03 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> Message-ID: Ok. In your example you have two levels of mirrors, root and banch. If we assume all mirrors are synced (exactly the same), the client (if it supports more than a preferred mirror) will check its mirrors in the order they are specified. So in your case, Y will check A. D. and E. in that order (assuming it checks all of its configured mirrors) If all mirrors are exactly the same however, it doesn't need to check A. D. and E. It only needs to check A. If A is down, it will check D. etc. If a change is made at the top level however, say an ESV update, there is a propigation time it takes for the mirrors to catch up. With high volume Linux mirrors this is minutes. If Crosswire were to have mirrors, it might have a policy that says something like mirrors are to syncronise no more than 24 hours no less than 6. That means in your demonstration it may take A. D. and E. upto 24 hours to reflect the change. Unlike Linux distributions however, its likely there can be some tollerance for such propigation effects. ~A On Mon, Jan 7, 2013 at 1:52 PM, DM Smith wrote: > I guess I need more information on mirrors. > > Let's say that there are to mirrors X and Y. For what ever reason, X has > A, B, C, D and Y has A, D, E. Software is configured to use Y. When it goes > to get a list of files, what does it get? If it requests B, what does it > get? Same questions for software configured for X and request for E. > > -- DM > > > On Jan 7, 2013, at 1:06 PM, Andrew Thule wrote: > > My experience with mirrors is that mirrors are done at the level of the > Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the > integrity and distribution of these things. > > That said, I think what you're saying is that you believe the Sword client > needs some additional support to support mirrors, and I don't think that's > entirely true. It may be that support for mirrors would be better > accomplished through additional patches, but as it stands now I get all of > Crosswire's modules as a proxy through either my public or private repo for > the very simply reason it's safer for me to do so. > > I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a > proxy), technically which means most clients (though perhaps not all) can > manage this. > > So I'm speaking specifically about Bibletime, Xiphos, Alkitab, > PocketSword, and Eloquent. If there are other clients out there, and > Crosswire pursues 'mirrors', that decision will influence development. > > ~A > > > On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: > >> Mirror management is a moot issue if the software doesn't support >> mirrors. I have no plans to add such to JSword, unless it is added to SWORD >> first. I highly doubt that it will be added to SWORD until a problem with >> resiliency creates a real need. Even then, I'm not sure that that will be >> used as a solution. >> >> In His Service, >> DM >> >> On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: >> >> DM, I agree that not having thought through mirror management >> procedurally (policy and best backpractice) is reason enough to hold off on >> such a venture, but those problems are typically trivial to solve given >> effective communication. >> >> Since technology is subordinat to intent, what needs to be worked out to >> move forward along these lines is the clarification of intent. >> >> If I were to look back on this recent discussion, I'd suggest a number >> of principles are already clear: >> -CrossWire resevers the right to approve or deny mirrors >> -CrossWire reserves the right to define which repositorories are >> considered "root" repositories (so authoritive) >> -Distribution of modules exclusively licensed to CrossWire should be >> retained by Crosswire >> -All Mirrors should take no longer than x (period of time) to accurately >> reflect 'root repositories' >> >> Etc. >> This issues have already (to some extent) been hashed through in debate, >> however discussion on the matter was limited, unproductive and unclear >> simply because of the degree of hostility the 'idea' of mirrors alone >> produced. >> >> If there had been an attitude of 'open but undecided' reservation about >> the matter, rather than outright 'hostility' its likely the issues you are >> raising now could have been dealt with more readily. >> >> ~A >> >> >> On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: >> >>> A few more reasons we discourage mirroring: >>> SWORD and JSword have no means for managing mirrors. They expect each >>> repository to be a unique collection of modules. >>> >>> A mirror that is partial, not containing all that is in the master >>> repository, probably will be confusing to users. >>> >>> A mirror that is hosted along with questionable modules probably will >>> give the appearance that CrossWire condones those modules. Especially when >>> the modules are in the same repository. >>> >>> In Him, >>> DM >>> >>> On Jan 4, 2013, at 9:09 AM, DM Smith wrote: >>> >>> From time to time, interest has been expressed in mirroring CrossWire's >>> SWORD modules. I thought I'd reiterate our policy. >>> >>> We strongly, very strongly, discourage mirroring of the SWORD module >>> repository. >>> >>> Those modules for which CrossWire has obtained distribution permission >>> from copyright holders must not be mirrored. These have >>> "DistributionLicense=Copyrighted; Permission to distribute granted to >>> CrossWire" in their conf. CrossWire maintains correspondence for each >>> of these modules. >>> >>> Mirrors are seldom current/correct, despite intentions. >>> >>> On occasion we have unintentionally hosted modules for which we did not >>> have permission. When presented with an ownership claim, we typically will >>> take the module offline immediately and validate the claim. If the claim is >>> false, we will put the module back up. If the claim is true, we obtain >>> permission before putting the module back online or we don't put it back. >>> This is an important part of our stewardship. >>> >>> If or when CrossWire has problems with distribution, we'll tackle the >>> problem at that time. Probably with a "Content Delivery Network" of >>> CrossWire owned servers. >>> >>> This or some variation of this probably should be in the wiki. >>> >>> In His Service, >>> DM >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Mon Jan 7 12:27:09 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Mon, 07 Jan 2013 20:27:09 +0100 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: <20130107192709.59500@gmx.net> > Von: Andrew Thule > It may be the case that the ISV foundations license to Crosswire is not as > restritive as Peter and Chris claimed and my action of sharing a compile > module on a separate server didn't in fact breach anything. Only by > inspecting Crosswire's license obligations can this be determined though. Now, imagine the ISV license to CrossWire did indeed say "You can obtain a random 'updated' text from somewhere else and publish it too, including other parts of the Bible than those we supplied you with. Any of the subscribers of your mailing list may do the same" And we forgot to share that info.... Oh, ouch! So when Random Dude publishes a module made up from random additional bits and publishes it on a random server under the name of ISV all kinds of people jumped down his throat and told him that he had no licence to do so and he might end up in trouble because he does something which is against the law, he might have had a defense but it was not accessible to him in that we did not publish along with our module the sentence: "You can obtain a random 'updated' text from somewhere else and publish it too, including other parts of the Bible than those we supplied you with. Any of the subscribers of your mailing list may do the same" " Oh, ouch! Now what exactly would Random Dude's best approach be? Given that he thinks he might just have more permissions that the default legal stance, as he suspects that CrossWire nefariously does not share all permissions they have. He might have asked from CrossWire before he published a random text with random additions on a random server. CrossWire might have told him "Oh, ouch! "We have indeed more permissions, and we need to update our module DistributionLicense". Or CrossWire might have told him - likely - "No, our license text is as it stands in the conf file". He might have asked from ISV. ISV might have told him "Go, do as you like". Or ISV might have told him - "No, we do not want you to publish a random text on a random server". Or ISV might have told him - "Here is a better text, use this one, and please add following license text to it" Oh, ouch! So, we have established Random Dude could have saved himself a lot of trouble by asking before he did something which on the face of it looked like A Bad Idea. But Random Dude did not ask before Now, as it stands, Random Dude feels aggrieved as he did something which looks like it was A Bad Idea. In his heart of hearts he feels it was a A Good Idea nevertheless, only all kinds of people tell him it was not. What pray, may Random Dude do now? He can take his random module from his random server and check again, does he have more rights than the law permits him as default? Maybe. Maybe not. CrossWire, assures him that he has not as far as they are concerned. So, what is left? He can go and ask ISV. Dear ISV, I have obtained from a random place a random document which looks pretty similar to your text. In fact it looks a lot better than what CrossWire has on its server. May I please pass it on via my server as something which looks like a CrossWire module? Or, alternatively could you even give me a better text than my random document? Love, hugs and kisses Random Dude It might work. Or it might not. Nevertheless. Bible publishers (unless they are of the more evil kind) do not behave music publishers and chances are Random Dude's actions, however ill advised they might have been, will not end up in court. So, not all is lost, Random Dude has learned that asking prior to doing things which on the face of it look like A Bad Thing, is always A Good Idea. Or maybe he has not learned and continues to blame everyone but himself. To be continued... From thulester at gmail.com Mon Jan 7 12:29:42 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 14:29:42 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: On Mon, Jan 7, 2013 at 1:44 PM, DM Smith wrote: > > > Each copyright owner has several fields in the conf that they can fill out > with that information. Most use the About field. A few use some other > fields. Consult the module's conf for the information that you want. If it > is not there then please assume that the owner did not want to share it or > did not provide it. > > It sounds like this process is not dealth with in a formal (meaning legal agreement) way. If that's the case the point is no clear terms of use have been established by the Copyright holder save for distribution which hasn't actually be defined (legally). This likely isn't idea from Crosswire's perspective. You might want to review this for the sake of formalization. Since this is the case, I won't question this further. > Have I come down hard on you? I know I have been direct and have tried to > be informative. > > No, and you've succeed in your goal. > We've only been talking about one part of the license agreement: the right > to re-distribute modules. We think that the DistributionLicense field > states it very well. > > DM, how Crosswire manages its licensing rights should probably be taken off-line and made internal. It seems to me you doesn't actually have a license, or at most a poorly defined one. If someone were to challenge Crosswire's right to 'distribute' Copyright text, Crosswire's bum would be better protected by having a license agreement, which terms (like distribution) defined, not simply an agreement in principle completed through attributes in a .conf file. Copyright and 'License to Distribute' are not attributes of configuration files, they are concepts covered by License agreements, and Law. > I don't think that is the case. I work on copyright modules and have never > seen a license agreement. I've never felt the need to see it. I always > treat a copyrighted work as a confidential, intellectual property to which > I only have sufficient privileges to do my work on the module. I'm sure > that I might be going beyond what is required, but I'd rather make that > mistake than betraying the owner's trust. > > Even Open-Source Software is covered by License Agreements. Surely you've heard of GNU General Public License (GPL), Apache License 2.0, MIT License. If you've ever worked on non-Open Source software, you've worked under a license of somesort or another (whether you saw it or not). Owners of intellectual propery, generally don't give up their intellectual propery rigths so freely. It may be true you've nevered read the license, but just about all software is covered under one license or another. Copyright Work is no different. > > Peter and Chris will have seen those agreements that they have > participated in obtaining. They have no need to have seen any others. > > I'm not doubting Peter and Chris have seen agreements, or the skill with which they navigate the sensitivies around obtaining permission to distribute Copyright Text. Rather, there's debate around whether my actions (posting a module to my repo) was reasonable. I'm claiming yes, given that the details of these agreements are not public. I assumed that if Crosswire has the right to distribute a module it has the right to distsribute a development module. > > Peter has told you privately of at least one that he was able to download. > Do you want that to be repeated here? > > Yes, I have no objection to it being repeated here. I don't believe I've received an email privately from Peter, though I'm filtering all SWORD Developers emails into one folder. It could have been private, but I didn't notices. Regardless, I'm not aware of any modules exclusive to Crosswire that were available. I believe mods.d.tar.gz could have falsely reported many as available which weren't, but no module (should have been) publicly obtainable, if one had tried (or my security is not up to snuff). If I've err'd in my security I have nothing to hide. I invite Peter or really anyone to let me know of my mistakes. An error however is not purposeful, and is correctable. > We accurately summarize it in the conf. We have explained it here. What is > hard about understanding that? What more is needed? > > The terms of rights and restrictions covered under a Copyright license however, are elements of the license, not a configuration file. No court in the would accept a .conf file as evidence Crosswire had the right to distribute Copyright Work. ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 12:37:17 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 14:37:17 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: Greg, respectfully you're still missing the point. Because a work is Copyright, doesn't grant Crosswire the right to inform me of anything, since CrossWire is not the CopyRight owner. It is only if the Copyright Owner grants Crosswire rights (and restrictions) though the use of a license to use the Copyright work that CrossWire has any legal obligations at all. The ISV's copyright found here: http://www.isv.org/legal.php Doesn't say anything about Crosswire's right to control how I distribute ISV text. If I am bound by the ISV's agreement only than if I abide by the terms of that agreement I can do anything the agreement allows me to do, and Crosswire has no say in the matter. However, because Crosswire is playing a role in the development of modules, I assumed (perhaps incorrectly) that Crosswire has 'license' to use the ISV as Copyright work, which means I am not bound by what is at the ISV site, but by the agreement Crosswire has with ISV. If CrossWire has no such agreements, I woudln't be touching any Copyrighted work for fear of the legal liabilities involved. Either Crosswire has Lisenses covering each Copyright work it deals with, or it does. If it doesn't there are larger problems than me sharing a module. If its does, those terms must be passed on with the work (under copyright law). ~A On Mon, Jan 7, 2013 at 2:02 PM, Greg Hellings wrote: > On Mon, Jan 7, 2013 at 12:43 PM, Andrew Thule wrote: > > Greg, its not clear you understand copyright law. > > > > Copyright Law is generic .. it applies generally. If you read American, > > Canadian, or European copyright law you won't find anything mentionion > > CrossWire, ISV, ESV specifically. That means it lays down principles. > > > > Therefore, copyright law with respect to either printed work or digital > work > > covers specifics in licenses. If you read the licensing that comes with > the > > ESV (found here http://www.esv.org/tools/licensing/ ) which is > specific, > > you'll see that nothing there says anything about CrossWire having the > right > > to distribute the ESV either, which means CrossWire's 'right' to > distribute > > the ESV (since the entire bible is being distributed) is covered under > its > > own license. > > > > Thefore anyone using CrossWire's ESV module, or developing that module > are > > bound by a license that is apparently 'confidential'. > > > > Therefore if I have done as I've claimed, and distributed the ISV in > > contravention of some law, you should be able to produce some document > that > > says I'm not permitted to do it. Since the Copyright act doesn't > > specifically speak about the ISV, you would presumably go to the ISV > > foundation site. Yes there is a document there (just like with the ESV), > > except it says nothing about CrossWire's right to distribute, so that > > license is not the one I've breached. For Crosswire to assert its > right to > > distribute the ISV it must have a license that says this, and that is > what > > we're talking about. > > The text is Copyrighted. CrossWire informs you of this in the conf > file. You are bound by whatever rights have been granted to you by the > holder of the ISV's Copyright. In this case, the text on the page you > reference is the ISV's generic rights that go out to anyone who > legally holds a copy of the text. You legally hold a copy of the text. > Therefore you are bound by that statement by the ISV's Copyright > holder. > > The rights that CrossWire has negotiated separately have no bearing on > your rights to use or distribute the text. Those rights apply to > CrossWire. You have no need to see the agreements because they in no > way have a bearing on you. You are neither CrossWire nor the publisher > of the ISV nor any legal or law enforcement organization within whose > jurisdiction any of the affected parties fall. > > That is how Copyright law works in the USA which is where CrossWire > falls. If you can point to a jurisdiction where you reside that is > affected by a law or requirement that Copyright agreements be made > public then you might have grounds for your request. Until then, you > are asking for private information which does not concern you. > > --Greg > > > > > ~A > > . > > > > > > On Mon, Jan 7, 2013 at 1:26 PM, Greg Hellings > > wrote: > >> > >> On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule > wrote: > >> > What I did have a hard time with was being publicly held accountable > to > >> > license restrictions reasonably unknown to me (and apparently secret), > >> > while > >> > having the issue made personal. It isn't reasonable to assume I knew > >> > sharing a compiled module with this group would set off a firestorm if > >> > the > >> > license between the ISV foundation and CrossWire is treated as > >> > confidential > >> > >> You're not being held accountable to CrossWire's terms of > >> distribution. You're being held accountable to Copyright law. > >> Something you are reasonably expected to know. But which you have > >> repeatedly shown yourself either unknowledgeable of - in the case of > >> the Dead Sea Scroll modules discussion - or unwilling to abide by > >> without some sort of extra treatment - in this case knowledge of a > >> contract between two parties which has no bearing on you. > >> > >> Stop trying to insult the rest of our intelligences by taking the > >> position of victim in this. You have shown flagrant disregard for > >> Copyright and an unwilling attitude to learn or be instructed in it. > >> > >> --Greg > >> > >> _______________________________________________ > >> sword-devel mailing list: sword-devel at crosswire.org > >> http://www.crosswire.org/mailman/listinfo/sword-devel > >> Instructions to unsubscribe/change your settings at above page > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 12:42:44 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 14:42:44 -0500 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: <20130107192709.59500@gmx.net> References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> <20130107192709.59500@gmx.net> Message-ID: Peter, The licenses found at the ISV site, and the ESV site do not specifically grant to you license to distribute their Copyrighted work. Those licensing don't mention CrossWire at all. I agree, that if I am bound by those licenses I have no right to distribute anything, but neither does CrossWire. Not only, but Crosswire has no right to chastise me for distributing them and is hipocritical if it does so. However, I'm giving Crosswire benefit of the doubt, that it has license to do what it is doing, and I was operating under those assumptions, in which case my actions should be gauged against what Crosswire has been licensed to do, not another license that grants neither of us permission to distribute anything. If I was mistaken to place my faith that Crosswire had actually obtained license to distribute copyrighted text (above and beyond the general license which prohibits that), oh dear (I'm not the only one with a problem then)! On Mon, Jan 7, 2013 at 2:27 PM, Peter von Kaehne wrote: > > > Von: Andrew Thule > > It may be the case that the ISV foundations license to Crosswire is not > as > > restritive as Peter and Chris claimed and my action of sharing a compile > > module on a separate server didn't in fact breach anything. Only by > > inspecting Crosswire's license obligations can this be determined though. > > Now, imagine the ISV license to CrossWire did indeed say > > "You can obtain a random 'updated' text from somewhere else and publish it > too, including other parts of the Bible than those we supplied you with. > Any of the subscribers of your mailing list may do the same" > > And we forgot to share that info.... > > Oh, ouch! > > So when Random Dude publishes a module made up from random additional bits > and publishes it on a random server under the name of ISV all kinds of > people jumped down his throat and told him that he had no licence to do so > and he might end up in trouble because he does something which is against > the law, he might have had a defense but it was not accessible to him in > that we did not publish along with our module the sentence: > > "You can obtain a random 'updated' text from somewhere else and publish it > too, including other parts of the Bible than those we supplied you with. > Any of the subscribers of your mailing list may do the same" " > > Oh, ouch! > > Now what exactly would Random Dude's best approach be? Given that he > thinks he might just have more permissions that the default legal stance, > as he suspects that CrossWire nefariously does not share all permissions > they have. > > He might have asked from CrossWire before he published a random text with > random additions on a random server. > > CrossWire might have told him "Oh, ouch! "We have indeed more permissions, > and we need to update our module DistributionLicense". > > Or CrossWire might have told him - likely - "No, our license text is as it > stands in the conf file". > > He might have asked from ISV. > > ISV might have told him "Go, do as you like". > > Or ISV might have told him - "No, we do not want you to publish a random > text on a random server". > > Or ISV might have told him - "Here is a better text, use this one, and > please add following license text to it" > > Oh, ouch! > > So, we have established Random Dude could have saved himself a lot of > trouble by asking before he did something which on the face of it looked > like A Bad Idea. > > But Random Dude did not ask before > > Now, as it stands, Random Dude feels aggrieved as he did something which > looks like it was A Bad Idea. In his heart of hearts he feels it was a A > Good Idea nevertheless, only all kinds of people tell him it was not. > > What pray, may Random Dude do now? > > He can take his random module from his random server and check again, does > he have more rights than the law permits him as default? > > Maybe. Maybe not. > > CrossWire, assures him that he has not as far as they are concerned. > > So, what is left? He can go and ask ISV. > > Dear ISV, > > I have obtained from a random place a random document which looks pretty > similar to your text. In fact it looks a lot better than what CrossWire has > on its server. May I please pass it on via my server as something which > looks like a CrossWire module? Or, alternatively could you even give me a > better text than my random document? > > Love, hugs and kisses > Random Dude > > It might work. Or it might not. > > Nevertheless. > > Bible publishers (unless they are of the more evil kind) do not behave > music publishers and chances are Random Dude's actions, however ill advised > they might have been, will not end up in court. So, not all is lost, Random > Dude has learned that asking prior to doing things which on the face of it > look like A Bad Thing, is always A Good Idea. > > Or maybe he has not learned and continues to blame everyone but himself. > > To be continued... > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 12:45:15 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 14:45:15 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> On Jan 7, 2013, at 1:19 PM, Andrew Thule wrote: > DM, all of which you said is reasonable; no issues from me. My point was in the efforts to assist with module develoment, I apparently crossed some line. I offered to send an OSIS update, and made a testing version of it available. The debate started (as you note) because of my making a testing version available (this taken to be 'distribution') I think what Greg responded is at the heart of the response. It was expressed very strongly here that your work on the DSS was a copyright infringement. You strongly disagreed. (Let's not get into that again.) You've hosted copyrighted modules from Wycliffe, IBT, bible.org and CrossWire. (I have not personally checked, so I may be wrong on repeating this.) I think this provoked history provoked the response you have gotten. While it has not been said (as far as I can remember), that you host any CrossWire module while hosting the DSS is highly undesirable to us as we think others may see it as condoning the DSS without a license agreement. When you posted the ISV, that became especially bothersome. Regarding module development of copyrighted material, the only proper way to proceed is using material supplied by the owner under license. Get permission first and then work on it. For modules that we already have, we need to use existing contacts to do that. Regarding the ESV that I'm working on, I was never given the contact information, but rather the last person to do the negotiation obtained new permission and granted me access to the source materials. Regarding copyrighted works that are not in the CrossWire repository, we need to work together to obtain permission. The proper way is to check the wiki, which has a page dedicated to such requests, and ask here whether any effort had been made in gaining permission. There are several here that have successfully gotten permission and can guide how to make such a request. We have a general wiki page giving a simple request. > > I don't have a hard time believing Crosswire has worked out the details of its licensing agreemnt to distribute the Copyright holder's text in through a very sensitive process (or even that these agreements come with residual sensitivies), even if I find it difficult to believe distribution of (complied) modules for the sake of development is expressly excluded or limited in otherways. > Public sharing of copyrighted modules is almost always a bad idea. Even when allowed, it may give the perception that we don't properly regard other license agreements. Private sharing with those who will participate in the development/QA, once permission has been obtained and registered with CrossWire, is good. > What I did have a hard time with was being publicly held accountable to license restrictions reasonably unknown to me (and apparently secret), while having the issue made personal. It isn't reasonable to assume I knew sharing a compiled module with this group would set off a firestorm if the license between the ISV foundation and CrossWire is treated as confidential .. IMHO, that's not what set off the firestorm. See above. > > Jerry, well I appreicate what you're saying, I suspect these issues are issues Crosswire needs to give more thought to internally so that module developers (volunteers, newcomers etc) are not expected to either provide the solution or get caught in the crossfire when a can-o-worms gets opened. > > ~A > > > > On Sun, Jan 6, 2013 at 1:27 PM, jhphx wrote: > On 1/6/2013 1:54 AM, Andrew Thule wrote: > I'm currently reviewing its contents to ensure no module exclusive to Crosswire was available. I will be putting it back up on completion of my review. > ... > > I am not sure how you think being exclusive to Crosswire works in this context, but, > > IF: > a) none of those other sources have legitimate (licensed) copies of a copyrighted text or it's derivatives, > OR > b) none of those sources provided you with a legitimate license to do whatever you do, > OR > c) it simply appears like you are violating anyone's copyrights, > THEN: > It won't matter to CrossWire how many other sources there are, you would appear to be, and in fact could be, a threat to CrossWire's ability to distribute if it appears that CrossWire is condoning what you do. It does not matter how the other sources see it, or how you see it, it matters how it seems to CrossWire and how it may seem to the publishers they work with. > > Andrew, you appear to want to help. There are many things someone like you could do, but maybe working on copyrighted modules and distribution of them is not the right task for now. There remains many other things needing to be done. > > If you still feel the need to work on a copyrighted text for CrossWire then I suggest you ask yourself three things: > a) could this work produce a copy, new copy, new version, or derivative of the text, > b) could this work result in exposing, intentionally or not, a copy so that wild (any unlicensed) distribution could result, > c) could this work possibly offend CrossWire or the publishers they work with. > > If the answer to any of those is yes then ask if you should work on it and exactly how you should do it to avoid these problems. Although, at this time "just ask" may be the best policy. > > Just a suggestion, I am not an official voice on these matters. > > Jerry > > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 12:50:27 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 14:50:27 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> Message-ID: On Jan 7, 2013, at 2:04 PM, Andrew Thule wrote: > Ok. In your example you have two levels of mirrors, root and banch. > > If we assume all mirrors are synced (exactly the same), the client (if it supports more than a preferred mirror) will check its mirrors in the order they are specified. This is precisely my point: Client software has to change. > > So in your case, Y will check A. D. and E. in that order (assuming it checks all of its configured mirrors) > If all mirrors are exactly the same however, it doesn't need to check A. D. and E. It only needs to check A. If A is down, it will check D. etc. > > If a change is made at the top level however, say an ESV update, there is a propigation time it takes for the mirrors to catch up. With high volume Linux mirrors this is minutes. If Crosswire were to have mirrors, it might have a policy that says something like mirrors are to syncronise no more than 24 hours no less than 6. > > That means in your demonstration it may take A. D. and E. upto 24 hours to reflect the change. Unlike Linux distributions however, its likely there can be some tollerance for such propigation effects. In my case, B is licensed only to CrossWire for distribution. E is the a module which has been added to one mirror but not on the master, say the DSS. These two are not true mirrors. SWORD and JSword can be configured with multiple repositories. They handle them differently. But suffice it to say that they expect that a module is in one and only one repository. The behavior is undefined if it occurs in more than one. > > ~A > > > > > On Mon, Jan 7, 2013 at 1:52 PM, DM Smith wrote: > I guess I need more information on mirrors. > > Let's say that there are to mirrors X and Y. For what ever reason, X has A, B, C, D and Y has A, D, E. Software is configured to use Y. When it goes to get a list of files, what does it get? If it requests B, what does it get? Same questions for software configured for X and request for E. > > -- DM > > > On Jan 7, 2013, at 1:06 PM, Andrew Thule wrote: > >> My experience with mirrors is that mirrors are done at the level of the Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the integrity and distribution of these things. >> >> That said, I think what you're saying is that you believe the Sword client needs some additional support to support mirrors, and I don't think that's entirely true. It may be that support for mirrors would be better accomplished through additional patches, but as it stands now I get all of Crosswire's modules as a proxy through either my public or private repo for the very simply reason it's safer for me to do so. >> >> I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a proxy), technically which means most clients (though perhaps not all) can manage this. >> >> So I'm speaking specifically about Bibletime, Xiphos, Alkitab, PocketSword, and Eloquent. If there are other clients out there, and Crosswire pursues 'mirrors', that decision will influence development. >> >> ~A >> >> >> On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: >> Mirror management is a moot issue if the software doesn't support mirrors. I have no plans to add such to JSword, unless it is added to SWORD first. I highly doubt that it will be added to SWORD until a problem with resiliency creates a real need. Even then, I'm not sure that that will be used as a solution. >> >> In His Service, >> DM >> >> On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: >> >>> DM, I agree that not having thought through mirror management procedurally (policy and best backpractice) is reason enough to hold off on such a venture, but those problems are typically trivial to solve given effective communication. >>> >>> Since technology is subordinat to intent, what needs to be worked out to move forward along these lines is the clarification of intent. >>> >>> If I were to look back on this recent discussion, I'd suggest a number of principles are already clear: >>> -CrossWire resevers the right to approve or deny mirrors >>> -CrossWire reserves the right to define which repositorories are considered "root" repositories (so authoritive) >>> -Distribution of modules exclusively licensed to CrossWire should be retained by Crosswire >>> -All Mirrors should take no longer than x (period of time) to accurately reflect 'root repositories' >>> >>> Etc. >>> This issues have already (to some extent) been hashed through in debate, however discussion on the matter was limited, unproductive and unclear simply because of the degree of hostility the 'idea' of mirrors alone produced. >>> >>> If there had been an attitude of 'open but undecided' reservation about the matter, rather than outright 'hostility' its likely the issues you are raising now could have been dealt with more readily. >>> >>> ~A >>> >>> >>> On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: >>> A few more reasons we discourage mirroring: >>> SWORD and JSword have no means for managing mirrors. They expect each repository to be a unique collection of modules. >>> >>> A mirror that is partial, not containing all that is in the master repository, probably will be confusing to users. >>> >>> A mirror that is hosted along with questionable modules probably will give the appearance that CrossWire condones those modules. Especially when the modules are in the same repository. >>> >>> In Him, >>> DM >>> >>> On Jan 4, 2013, at 9:09 AM, DM Smith wrote: >>> >>>> From time to time, interest has been expressed in mirroring CrossWire's SWORD modules. I thought I'd reiterate our policy. >>>> >>>> We strongly, very strongly, discourage mirroring of the SWORD module repository. >>>> >>>> Those modules for which CrossWire has obtained distribution permission from copyright holders must not be mirrored. These have "DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire" in their conf. CrossWire maintains correspondence for each of these modules. >>>> >>>> Mirrors are seldom current/correct, despite intentions. >>>> >>>> On occasion we have unintentionally hosted modules for which we did not have permission. When presented with an ownership claim, we typically will take the module offline immediately and validate the claim. If the claim is false, we will put the module back up. If the claim is true, we obtain permission before putting the module back online or we don't put it back. This is an important part of our stewardship. >>>> >>>> If or when CrossWire has problems with distribution, we'll tackle the problem at that time. Probably with a "Content Delivery Network" of CrossWire owned servers. >>>> >>>> This or some variation of this probably should be in the wiki. >>>> >>>> In His Service, >>>> DM >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Mon Jan 7 12:54:25 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Mon, 07 Jan 2013 20:54:25 +0100 Subject: [sword-devel] Exclusive Rights Granting Crosswire License to Distribute In-Reply-To: References: <5523D925-5FE1-4604-AFB8-AEECEC0CFB06@crosswire.org> Message-ID: <50EB27F1.6020404@crosswire.org> Andrew and others, This thread is counterproductive-- and has been for quite some time. It is now closed. I was CC:ed on the email Peter sent you (Andrew) privately which outlines explicitly how he was able to obtain multiple modules from your mirror which indeed have: DistributionLicense=Copyrighted; Permission to distribute granted to CrossWire The email gave step by step instructions how to reproduce the download, which consisted simply of adding your mirror for use by the SWORD InstallManager command line interface and using the standard lookup and install commands. I give you the benefit of the doubt that you innocently and simply didn't know that removing the mods.d/*.conf file was not enough to avoid listing the module as available for download (it was still in the cache mods.d.tar.gz file and the data files available in the modules/* folder) Please removed all modules from your mirrors for which you have not obtained redistribution licenses personally. If you fail to do so (which I give you the benefit of the doubt and hope you will comply), since the URL was posted publicly on this list, you will be banned from further posting to this list. At the risk of assuming I can reword the sentiments of other on this thread, to make things obvious to you: I believe you need to invert your thinking about copyright restrictions. Try starting with 0 (zero) rights, and then build on that from what you read in the license. So, in other words: If a work is (C) Copyrighted by the creator. You should start by assuming you have no rights to copy the work and certainly no rights to DISTRIBUTE THE WORK FOR ANY PURPOSE (distributing is a superset of copying, so this should make sense in set theory). CrossWire starts this way too. We assume we have no rights to copy or publicly distribute any copyrighted work unless we gain permission from the copyright holder. When a copyright owner grants CrossWire permission to copy and distribute, we define this as: making the text publicly available from "*.crosswire.org". This does not mean our USERS can copy the work or publicly redistribute the work by making the text available to others; it simply means the CrossWire can copy the work and distribute it to our users. Some of our agreements do explicitly allow redistribution and we state that to our users. We assume all our users assume they start with 0 (zero) rights to copy and distribute the text. We feel they can safely understand any of these rights conveyed by the entry in the module's DistributionLicense field: http://crosswire.org/wiki/DevTools:conf_Files#DistributionLicense If a right to copy and distribute is not explicitly granted, then our users should assume they do not have these DISTRIBUTION rights, unless they are told otherwise by the publisher. (As DM has pointed out, some publishers grant further rights in the "About" section of our .conf file, e.g., "Permission to use up to 500 words... blah blah"). But if you're looking for an overall distribution license for the entire module that is conveyed from the publisher through CrossWire to the end user, this would be summarized in the DistributionLicense field. If you've not been granted your own permission to copy and distribute a text by the publisher directly, then you likely do not have that permission and should always begin by assuming that you do not have permission unless you have explicitly seen it granted to you. Hope this helps summarize this thread and represents the general thoughts of everyone who have spoken with you regarding copyright in general and the policy we have against posting of public links on this mailing list to copies of our modules which are copyrighted by publishers who have not granted redistribution rights through CrossWire (as would be expressly seen in the DistributionLicense field if re-distribution rights had been granted). Please cease posting on this topic and please remove the modules. Thank you, Troy On 01/07/2013 07:53 PM, Andrew Thule wrote: > Chris this list in an of itself is not sufficient (legally) to > establish these principles. It is the Copyright owners who make this > determination, not Crosswire list members. > Each Copyright owner is entitled to impose unique restrictions on the > use of their texts. CrossWire is bound on a module by module basis to > abide by the license agreement agreed to by the Copyright owner. > (Although these agreements may be smiliar, I doubt very much they are > exactly the same. You can see from comparing ESV's general license to > ISVs general license (found under legal) they differ. > It may be the case that the ISV foundations license to Crosswire is > not as restritive as Peter and Chris claimed and my action of sharing > a compile module on a separate server didn't in fact breach anything. > Only by inspecting Crosswire's license obligations can this be > determined though. > Now that I've been tarred and feathered, I would kind of like to know > if Crosswires license to distrbiute the ISV indeed prohibits this (so > I can know if I'm guilty as charged or not). Also, if no such > restriction exists, Peter's claim that I have no right to distribute > the ISV doesn't hold, and I'll consider continuing to server it on my > repo. > ~A > > > On Mon, Jan 7, 2013 at 1:19 PM, Chris Burrell > wrote: > > I think we've got the answers across multiple threads. DM answers > your question in my thread. others in other threads. > > 1. All modules are fair game for sword front ends to use and display. > > 2. Modifying modules and/or redistributing is not allowed for > modules marked as Copyrighted permission granted CrossWire > > 3. Conf files are occasionally inconsistent in the copyright > field and therefore setting up mirrors is strongly discouraged as > mirror owners may well end up hosting modules illegally. This > threatens the ongoing relationship between CrossWire and the > publishers. > > 4. Modifying modules in general is discouraged as a lonesome task > as there are often tools used to generate these modules and > therfore the source may not be available to the keen module > editor. There may also be extra restrictions on this modules which > restrict the type of modifications, e.g. adding strong numbers > > 5. As a result of 4, everyone is encouraged to contact Chris L to > find out who the 'owner' of a module is before making any > modifications but will then be encouraged to participate is > circumstances allow. > > 6. Sword and JSword so not cope well with repositories hosting the > same module. This is a further reason for discouraging the > instalation of Mirrors for public use. > > Hope that is a good summary of the discussion so far. > > Chris > > On 7 Jan 2013 17:59, "Andrew Thule" > wrote: > > > On Sun, Jan 6, 2013 at 11:12 AM, DM Smith > > wrote: > > No, we cannot publish the terms of licensing agreements. > Think about it. These are confidential, privileged > contracts between organizations. > > Umm, with software Licenses, Acceptable Use Policies, > Copyright Restrictions and Copyright limitations are not > typically priviledge .. > The contractual agreement itself may be, but License for use, > especially in public forums is not, otherwise how can you come > down so hard on someone like me for trying to abide > by licensing agreement when those agreements are not know? > You're saying on the one had I have to abide by Crosswire's > agreement with the Copyright Owner and on the other hand I > cannot know what those provisions are. > I think if you check the contract, you'll see the actually > license agreement as an Appendix or something of that sort for > this very reason. > > > The contracts are dictated by the publishers. When asked > what they need to say, we provide the broadest description > of what they need to say at minimum, but we don't ever > suggest particular wording or terms. If the terms are > unacceptable to us, we communicate that clearly and let > them either amend their terms or withdraw the module. > > Yes, true, however Crosswire as the licensee is not dealing > with paper, but with digital forms of the text, so > presumably as the licensee you've worked through some of the > issues related to dealing with 'digial format'. At least > your this recent business between Chris, Peter and I suggests > that this is the case. > Although the terms of Crosswire license to use of these > Copyright works are not clear to me (dispite what Chris > and Peter would have you believe) because I've seen no such > terms, they are apparently clear to Chris and Peter. I have > no trouble believing Chris and Peter have seen them, or they > wouldn't be calling me to account. > > We only need to prove our assertion with the publishers. > Which we have do on occasion. > > Agreed. > > > The wording of your request is inviting a "go pound sand" > response. Please be careful in how you word things. > > DM, I will be careful how I word things because such advice is > always prudent advice. > That said, I deny I was telling anyone to 'pound sand'. I am > disappointed at the way my character, purpose, and > contribution is contantly maligned in these discussions. It > send the signal that 'new-comers' and their ideas are not > welcome here dispite the claim this is an open community. This > treatment on the part of some is not uniform by any means. > However the method of dealing with conflict among Christian's > is covered in the bible, and my disappointment stems from the > idea that not all who engage in these disagreements make > efforts to disagree on biblical principles. (I assume > everyone here is a Christian). > For example, I am particularly disappointed that I was accused > of breaking Crosswire's licensing restrictions, yet no one has > bothered to either publically name one module that was > available at my repo that should have been, or provide access > to Crosswire's license as evidence this was wrong. > If Crosswire has legitimate license to distribution Copyright > text and is going to use this license agreement like a hammer, > it's not unrasonable to ask that it be made public, otherwise > it has no right to defer to it in issues of disagreement. > ~A > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5001 at hotmail.com Mon Jan 7 13:02:48 2013 From: 5001 at hotmail.com (Pola Edward) Date: Mon, 7 Jan 2013 22:02:48 +0200 Subject: [sword-devel] Complete Osis Commentary Example Message-ID: Hi, Sorry for sending this to the wrong list, but this list is more active than osis-users list , My previous post in osis-users list didn't got attention and i got just 2 replies and no one replied after my last reply . The problem still exists and I've made many many trials, trying to get it to work the wiki doesn't contain a complete osis commentary example like bibles section the following is a complete osis structure i tried, it appears in xiphos and BPBible, but no effect for titles, bold and underline tags, all texts appear the same in the output . in programs like Bible Time, I see xml structure instead of normal texts Please send me a Complete Osis Commentary Example, so I can follow it
????? ????? ????? ????? ???? Bible.FrTadros Bible.KJV Bible.KJV
This is a title, and supposed to be bold and underlined

blah blah blah blah blah blah Please see James 1:19

-------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Mon Jan 7 13:05:07 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 7 Jan 2013 14:05:07 -0600 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> Message-ID: On Mon, Jan 7, 2013 at 1:37 PM, Andrew Thule wrote: > Greg, respectfully you're still missing the point. > > Because a work is Copyright, doesn't grant Crosswire the right to inform me > of anything, since CrossWire is not the CopyRight owner. Correct. Nor does it mean CrossWire is required to inform you of anything - such as its own license agreement. > > It is only if the Copyright Owner grants Crosswire rights (and restrictions) > though the use of a license to use the Copyright work that CrossWire has any > legal obligations at all. Yes, and CrossWire has a private agreement with the ISV publishers to publish the ISV text in its module. > > The ISV's copyright found here: > http://www.isv.org/legal.php CrossWire's private agreement with the publisher applies beyond these general rights to CrossWire's use of the text. The above rights apply to your use of the text. And to mine. And to DM's. And to Chris Little's. And to Peter's. Unless one of us has acquired a separate agreement, none of us may distribute or use the ISV text in any way other than what is detailed at http://www.isv.org/legal.php. CrossWire is not limited to the text of that URL because it has been granted exception to that general clause. You have not, and thus may not offer the text anymore than I may do so because I have not gained permission. Even if I am working on a module for CrossWire, under CrossWire's auspices, I am not permitted to publish a copy of that myself. This is exactly what you have done. Last year I had in my possession about 1000 modules under Copyright by different people and organizations. The intention was that these modules would be transformed into SWORD modules for the organization that had rights to do this. Despite being a part of that organization as a volunteer, I was not able to send copies of the modules to Troy or Karl or Chris or anyone else when I ran into problems because none of them are members of that organization. Once the conversion was completed, I was not permitted to send a copy of those modules to the QA and test people because I am not that organization. Since I'm not actively working on those modules any longer I have removed them from my local machines so that even my personal friends that I grant SSH access to my home computer would not inadvertently acquire copies of them. All because I had no right to distribute those modules any more than you had a right to distribute the ISV. I never had to see that organization's specific agreement with each publisher for each of those 1000 works to know that I, as a private individual, am not governed by the private agreement that organization has with each publisher. But for some reason you think you need to know the text of a private agreement to know that your use is governed by Copyright law. Let me provide you a good rule-of-thumb, so you can avoid making a fool of yourself again in the future: If you have not received a notice - specific like CrossWire's or generic like the one on the ISV's website - from the Copyright holder granting you permission to distribute a work then you do not have permission to distribute that work to anyone for any purpose. Yes, there are some exceptions to this, but you've already proven you don't know what those exceptions are or when they apply to you. > > Doesn't say anything about Crosswire's right to control how I distribute ISV > text. If I am bound by the ISV's agreement only than if I abide by the > terms of that agreement I can do anything the agreement allows me to do, and > Crosswire has no say in the matter. CrossWire has no right to control your distribution of the ISV text. We're not asserting we have that right. We're trying to tell you that you also don't have that right nor do you have a right to distribute it (unless you're hiding from us the fact that you have negotiated distribution rights, in which case I apologize for being wrong and I'm sure everyone else here would as well). We can't control your distribution - only the Copyright holder can do so through the proper legal channels. > > However, because Crosswire is playing a role in the development of modules, > I assumed (perhaps incorrectly) that Crosswire has 'license' to use the ISV > as Copyright work, which means I am not bound by what is at the ISV site, > but by the agreement Crosswire has with ISV. It does have that right. Are you CrossWire? No. So why would you assume that CrossWire's right extended to you? > > If CrossWire has no such agreements, I woudln't be touching any Copyrighted > work for fear of the legal liabilities involved. It does have that right. Do you? Because that's what actually the issue here. > > Either Crosswire has Lisenses covering each Copyright work it deals with, or > it does. If it doesn't there are larger problems than me sharing a module. > If its does, those terms must be passed on with the work (under copyright > law). Multiple people have assured you that CrossWire is very careful to have such licenses. If you are acting as an agent of a Copyright holder and present the proper requirements then CrossWire will produce proof of that license. But none of that has an affect on whether or not you have a right to deal with the ISV in the way you did. --Greg From thulester at gmail.com Mon Jan 7 13:09:39 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 15:09:39 -0500 Subject: [sword-devel] ISV status? In-Reply-To: <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> References: <50E9C213.5060301@cox.net> <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> Message-ID: DM, Let's not reopen the DSS issue, thought it is the same issue. Crosswire is not the Copyright Owner of a single DSS translations. So as long as Crosswire is playing no official role in their digitization or distribution, CrossWire has absolutely nothing to say on the matter. That said, I was seeking assistance. That formally would have required anyone helping me would have had to been brougt under the some terms, which means I would likely have had to 'legally' clarify the terms of the work (by doing exactly what I'm asking CrossWire to do now, by providing a license). Since CrossWire did not get involved, Crosswire has absolutely no idea what license restrictions there are NOT or ARE in dealing with the source text (only speculation), or even if I do in fact have license (though I argued restrictions were exempted by law) . Until a Crosswire developere had actually engaged for the sake of making this a Crosswire module to be reposed at Crosswire's repot - Crosswire was foolish to argue the point ... ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Mon Jan 7 13:18:44 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 7 Jan 2013 15:18:44 -0500 Subject: [sword-devel] ISV status? In-Reply-To: References: <50E9C213.5060301@cox.net> <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> Message-ID: <81BD2FB3-B230-4DCA-9923-AD705DC05256@crosswire.org> On Jan 7, 2013, at 3:09 PM, Andrew Thule wrote: > Let's not reopen the DSS issue Agreed. I think that it was the foundation for the tone of responses you received. I think it was the elephant in the room. I thought you'd like to know that. In Him, DM -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Mon Jan 7 13:19:08 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Mon, 7 Jan 2013 20:19:08 +0000 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> Message-ID: I concur with DM, the Sword/JSword/UIs would have to change. I've had that issue with having modules in both the normal repo and the (old?) beta repository. The frontends give a false impression as to which module came from which repository. On 7 January 2013 19:50, DM Smith wrote: > > On Jan 7, 2013, at 2:04 PM, Andrew Thule wrote: > > Ok. In your example you have two levels of mirrors, root and banch. > > If we assume all mirrors are synced (exactly the same), the client (if it > supports more than a preferred mirror) will check its mirrors in the order > they are specified. > > > This is precisely my point: Client software has to change. > > > So in your case, Y will check A. D. and E. in that order (assuming it > checks all of its configured mirrors) > If all mirrors are exactly the same however, it doesn't need to check A. > D. and E. It only needs to check A. If A is down, it will check D. etc. > > If a change is made at the top level however, say an ESV update, there is > a propigation time it takes for the mirrors to catch up. With high volume > Linux mirrors this is minutes. If Crosswire were to have mirrors, it might > have a policy that says something like mirrors are to syncronise no more > than 24 hours no less than 6. > > That means in your demonstration it may take A. D. and E. upto 24 hours to > reflect the change. Unlike Linux distributions however, its likely there > can be some tollerance for such propigation effects. > > > In my case, B is licensed only to CrossWire for distribution. E is the a > module which has been added to one mirror but not on the master, say the > DSS. These two are not true mirrors. > > SWORD and JSword can be configured with multiple repositories. They handle > them differently. But suffice it to say that they expect that a module is > in one and only one repository. The behavior is undefined if it occurs in > more than one. > > > ~A > > > > > On Mon, Jan 7, 2013 at 1:52 PM, DM Smith wrote: > >> I guess I need more information on mirrors. >> >> Let's say that there are to mirrors X and Y. For what ever reason, X has >> A, B, C, D and Y has A, D, E. Software is configured to use Y. When it goes >> to get a list of files, what does it get? If it requests B, what does it >> get? Same questions for software configured for X and request for E. >> >> -- DM >> >> >> On Jan 7, 2013, at 1:06 PM, Andrew Thule wrote: >> >> My experience with mirrors is that mirrors are done at the level of the >> Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the >> integrity and distribution of these things. >> >> That said, I think what you're saying is that you believe the Sword >> client needs some additional support to support mirrors, and I don't think >> that's entirely true. It may be that support for mirrors would be better >> accomplished through additional patches, but as it stands now I get all of >> Crosswire's modules as a proxy through either my public or private repo for >> the very simply reason it's safer for me to do so. >> >> I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a >> proxy), technically which means most clients (though perhaps not all) can >> manage this. >> >> So I'm speaking specifically about Bibletime, Xiphos, Alkitab, >> PocketSword, and Eloquent. If there are other clients out there, and >> Crosswire pursues 'mirrors', that decision will influence development. >> >> ~A >> >> >> On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: >> >>> Mirror management is a moot issue if the software doesn't support >>> mirrors. I have no plans to add such to JSword, unless it is added to SWORD >>> first. I highly doubt that it will be added to SWORD until a problem with >>> resiliency creates a real need. Even then, I'm not sure that that will be >>> used as a solution. >>> >>> In His Service, >>> DM >>> >>> On Jan 7, 2013, at 12:39 PM, Andrew Thule wrote: >>> >>> DM, I agree that not having thought through mirror management >>> procedurally (policy and best backpractice) is reason enough to hold off on >>> such a venture, but those problems are typically trivial to solve given >>> effective communication. >>> >>> Since technology is subordinat to intent, what needs to be worked out to >>> move forward along these lines is the clarification of intent. >>> >>> If I were to look back on this recent discussion, I'd suggest a number >>> of principles are already clear: >>> -CrossWire resevers the right to approve or deny mirrors >>> -CrossWire reserves the right to define which repositorories are >>> considered "root" repositories (so authoritive) >>> -Distribution of modules exclusively licensed to CrossWire should be >>> retained by Crosswire >>> -All Mirrors should take no longer than x (period of time) to accurately >>> reflect 'root repositories' >>> >>> Etc. >>> This issues have already (to some extent) been hashed through in debate, >>> however discussion on the matter was limited, unproductive and unclear >>> simply because of the degree of hostility the 'idea' of mirrors alone >>> produced. >>> >>> If there had been an attitude of 'open but undecided' reservation about >>> the matter, rather than outright 'hostility' its likely the issues you are >>> raising now could have been dealt with more readily. >>> >>> ~A >>> >>> >>> On Sun, Jan 6, 2013 at 2:17 PM, DM Smith wrote: >>> >>>> A few more reasons we discourage mirroring: >>>> SWORD and JSword have no means for managing mirrors. They expect each >>>> repository to be a unique collection of modules. >>>> >>>> A mirror that is partial, not containing all that is in the master >>>> repository, probably will be confusing to users. >>>> >>>> A mirror that is hosted along with questionable modules probably will >>>> give the appearance that CrossWire condones those modules. Especially when >>>> the modules are in the same repository. >>>> >>>> In Him, >>>> DM >>>> >>>> On Jan 4, 2013, at 9:09 AM, DM Smith wrote: >>>> >>>> From time to time, interest has been expressed in mirroring CrossWire's >>>> SWORD modules. I thought I'd reiterate our policy. >>>> >>>> We strongly, very strongly, discourage mirroring of the SWORD module >>>> repository. >>>> >>>> Those modules for which CrossWire has obtained distribution permission >>>> from copyright holders must not be mirrored. These have >>>> "DistributionLicense=Copyrighted; Permission to distribute granted to >>>> CrossWire" in their conf. CrossWire maintains correspondence for each >>>> of these modules. >>>> >>>> Mirrors are seldom current/correct, despite intentions. >>>> >>>> On occasion we have unintentionally hosted modules for which we did not >>>> have permission. When presented with an ownership claim, we typically will >>>> take the module offline immediately and validate the claim. If the claim is >>>> false, we will put the module back up. If the claim is true, we obtain >>>> permission before putting the module back online or we don't put it back. >>>> This is an important part of our stewardship. >>>> >>>> If or when CrossWire has problems with distribution, we'll tackle the >>>> problem at that time. Probably with a "Content Delivery Network" of >>>> CrossWire owned servers. >>>> >>>> This or some variation of this probably should be in the wiki. >>>> >>>> In His Service, >>>> DM >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Mon Jan 7 13:21:04 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Mon, 07 Jan 2013 21:21:04 +0100 Subject: [sword-devel] *THREAD CLOSED * (was: ISV status?) In-Reply-To: References: <50E9C213.5060301@cox.net> <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> Message-ID: <50EB2E30.5070101@crosswire.org> The previous directive to close these discussions extends to this thread, as well. The same conditions apply for action: CrossWire considers the DSS materials you post on your website to be under copyright and not legal for you to distribute. Our policy is to not allow illegal content to be posted or linked to on sword-devel. Please refrain from making this material available from the link you have posted here on sword-devel or your ability to post to sword-devel will be revoked. Sincerely, with all good wishes, Troy On 01/07/2013 09:09 PM, Andrew Thule wrote: > DM, > Let's not reopen the DSS issue, thought it is the same issue. > Crosswire is not the Copyright Owner of a single DSS translations. So > as long as Crosswire is playing no official role in their digitization > or distribution, CrossWire has absolutely nothing to say on the matter. > That said, I was seeking assistance. That formally would have > required anyone helping me would have had to been brougt under the > some terms, which means I would likely have had to 'legally' clarify > the terms of the work (by doing exactly what I'm asking CrossWire to > do now, by providing a license). > Since CrossWire did not get involved, Crosswire has absolutely no idea > what license restrictions there are NOT or ARE in dealing with the > source text (only speculation), or even if I do in fact have license > (though I argued restrictions were exempted by law) . > Until a Crosswire developere had actually engaged for the sake of > making this a Crosswire module to be reposed at Crosswire's repot - > Crosswire was foolish to argue the point ... > ~A > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 14:51:29 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 16:51:29 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> Message-ID: If you think about Linux distributions, you see a number of approaches: 1 Software makes the mirror selection 2 User makes Mirror selection. Given the clients cited above, only if the Software chooses the mirror are coding changes necessary. The Software developer must also make decisions about the mirrors are checked. As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. That said, I have no doubt there are clients out there that need better support for mirror configuration. That's not going to happen until Crosswire mirrors exist however. ~A On Monday, January 7, 2013, Chris Burrell wrote: > I concur with DM, the Sword/JSword/UIs would have to change. I've had that > issue with having modules in both the normal repo and the (old?) beta > repository. The frontends give a false impression as to which module came > from which repository. > > > > On 7 January 2013 19:50, DM Smith wrote: > > > On Jan 7, 2013, at 2:04 PM, Andrew Thule wrote: > > Ok. In your example you have two levels of mirrors, root and banch. > > If we assume all mirrors are synced (exactly the same), the client (if it > supports more than a preferred mirror) will check its mirrors in the order > they are specified. > > > This is precisely my point: Client software has to change. > > > So in your case, Y will check A. D. and E. in that order (assuming it > checks all of its configured mirrors) > If all mirrors are exactly the same however, it doesn't need to check A. > D. and E. It only needs to check A. If A is down, it will check D. etc. > > If a change is made at the top level however, say an ESV update, there is > a propigation time it takes for the mirrors to catch up. With high volume > Linux mirrors this is minutes. If Crosswire were to have mirrors, it might > have a policy that says something like mirrors are to syncronise no more > than 24 hours no less than 6. > > That means in your demonstration it may take A. D. and E. upto 24 hours to > reflect the change. Unlike Linux distributions however, its likely there > can be some tollerance for such propigation effects. > > > In my case, B is licensed only to CrossWire for distribution. E is the a > module which has been added to one mirror but not on the master, say the > DSS. These two are not true mirrors. > > SWORD and JSword can be configured with multiple repositories. They handle > them differently. But suffice it to say that they expect that a module is > in one and only one repository. The behavior is undefined if it occurs in > more than one. > > > ~A > > > > > On Mon, Jan 7, 2013 at 1:52 PM, DM Smith wrote: > > I guess I need more information on mirrors. > > Let's say that there are to mirrors X and Y. For what ever reason, X has > A, B, C, D and Y has A, D, E. Software is configured to use Y. When it goes > to get a list of files, what does it get? If it requests B, what does it > get? Same questions for software configured for X and request for E. > > -- DM > > > On Jan 7, 2013, at 1:06 PM, Andrew Thule wrote: > > My experience with mirrors is that mirrors are done at the level of the > Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the > integrity and distribution of these things. > > That said, I think what you're saying is that you believe the Sword client > needs some additional support to support mirrors, and I don't think that's > entirely true. It may be that support for mirrors would be better > accomplished through additional patches, but as it stands now I get all of > Crosswire's modules as a proxy through either my public or private repo for > the very simply reason it's safer for me to do so. > > I have no trouble getting Sword/Crosswire modules from a 'mirror' (as a > proxy), technically which means most clients (though perhaps not all) can > manage this. > > So I'm speaking specifically about Bibletime, Xiphos, Alkitab, > PocketSword, and Eloquent. If there are other clients out there, and > Crosswire pursues 'mirrors', that decision will influence development. > > ~A > > > On Mon, Jan 7, 2013 at 12:55 PM, DM Smith wrote: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niccarter at mac.com Mon Jan 7 15:13:36 2013 From: niccarter at mac.com (Nic Carter) Date: Tue, 08 Jan 2013 09:13:36 +1100 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> Message-ID: <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> Sent from my phone, hence this email may be short... On 08/01/2013, at 8:51, Andrew Thule wrote: > > As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. Yup, policy is no mirrors at this point in time. It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. Easy :) Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) From thulester at gmail.com Mon Jan 7 15:58:52 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 17:58:52 -0500 Subject: [sword-devel] *THREAD CLOSED * (was: ISV status?) In-Reply-To: <50EB2E30.5070101@crosswire.org> References: <50E9C213.5060301@cox.net> <01AE2FA8-85D4-4452-8BFC-351A9048BFD1@crosswire.org> <50EB2E30.5070101@crosswire.org> Message-ID: Troy, CrossWire is itself distributing Copyright Material, unwilling to provide evidence it posses License to do this. Therefore since you're accusing me of this same thing, the same standard applies. Although I don't impose ultimatums on CrossWire though you are with me, feel free to validate your suspicion about the Dead Sea Scroll module with each Copyright holders directly. If a single Copyright holder is found who denies I have right to construct a module from a textual derivative of their work, I will do exactly as you ask, and beg forgiveness. However, because CrossWire isn't the Copyright owner (whatever it considers), and has nothing to do with the non-Crosswire server hosting the module (by its own choice) and doesn't even represent the Copyright interests of the source material, you might want to check with the actual Copyright holders on what they've allowed, before acting on your hunch. To remove a volunteer's posting privileges on a hunch without warrant (especially if you're mistaken) would be arbitrarily unjust and capricious, given that CrossWire's own right to distribute Copyrighted text is also still unproven and in question (though equally strongly claimed). Even so, as the list manager, feel free to do as you see fit (though have courage enough to do it publicly). With equally good wishes, and also with sincerity. ~A On Monday, January 7, 2013, Troy A. Griffitts wrote: > The previous directive to close these discussions extends to this > thread, as well. The same conditions apply for action: > > CrossWire considers the DSS materials you post on your website to be under > copyright and not legal for you to distribute. Our policy is to not allow > illegal content to be posted or linked to on sword-devel. Please refrain > from making this material available from the link you have posted here on > sword-devel or your ability to post to sword-devel will be revoked. > > Sincerely, with all good wishes, > > Troy > > > > On 01/07/2013 09:09 PM, Andrew Thule wrote: > > DM, > > Let's not reopen the DSS issue, thought it is the same issue. Crosswire > is not the Copyright Owner of a single DSS translations. So as long as > Crosswire is playing no official role in their digitization or > distribution, CrossWire has absolutely nothing to say on the matter. > > That said, I was seeking assistance. That formally would have required > anyone helping me would have had to been brougt under the some terms, which > means I would likely have had to 'legally' clarify the terms of the work > (by doing exactly what I'm asking CrossWire to do now, by providing a > license). > > Since CrossWire did not get involved, Crosswire has absolutely no idea > what license restrictions there are NOT or ARE in dealing with the source > text (only speculation), or even if I do in fact have license (though I > argued restrictions were exempted by law) . > > Until a Crosswire developere had actually engaged for the sake of making > this a Crosswire module to be reposed at Crosswire's repot - Crosswire was > foolish to argue the point ... > > ~A > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Mon Jan 7 16:09:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Mon, 7 Jan 2013 18:09:03 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> Message-ID: Agreed. That's another way of stating it: until Crosswire decides on the issue, there's no sense in developers discussing it.. ~A On Monday, January 7, 2013, Nic Carter wrote: > > Sent from my phone, hence this email may be short... > > On 08/01/2013, at 8:51, Andrew Thule > > wrote: > > > > > As long as Crosswire has policies in place govererning official mirrors > there should no no worries mirrors are out of sync, in which case preferred > mirror selection can be left to the user, and indeed mirror checking > behaviour configurable. > > Yup, policy is no mirrors at this point in time. > It is thought that there _may_ be room in the future for some, but these > will be done from a *.crosswire.org domain so as to satisfy copyright > requirements. > > Easy :) > > Thanks for your thoughts & I'm glad we can now put this discussion to > rest. :) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampster at gmail.com Mon Jan 7 18:22:38 2013 From: trampster at gmail.com (Daniel Hughes) Date: Tue, 8 Jan 2013 14:22:38 +1300 Subject: [sword-devel] local cache of module text Message-ID: I have finally found time to start looking at adding sword module support to Wide Margin (http:\\widemargin.org) again. And I have a question about copyright and licencing. Currently Wide Margin uses a sqlite database to store it's bible text. The database is full text indexed which provides the performance required to achieve as you type searching. (I do understand sword supports optional indexing which should achieve the same performance) Am I allowed to pull the text out of the sword module once it is installed (using the sword libs) and put it in my local sqlite database. This would be the lest path of resistance for getting sword module support in my application. It would also limit the amount of c# swig bindings I will need (I have enough working to get the text but that's it, the bindings are proving problematic.) To be clear the use of the sqlite database would be transparent to the user. They would install the sword module and then the application would import the text into it's sqlite database. I don't want to go any further with the work until I know that this is not in violation of the copyright/licencing of the modules. Cheers, Daniel Hughes -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Tue Jan 8 00:51:01 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Tue, 08 Jan 2013 08:51:01 +0100 Subject: [sword-devel] local cache of module text In-Reply-To: References: Message-ID: <20130108075101.213060@gmx.net> > Von: Daniel Hughes > Am I allowed to pull the text out of the sword module once it is installed > (using the sword libs) and put it in my local sqlite database. Not a lawyer, so my advice might be of limited value. Many of our modules are public domain and essentially you can do as you like. Many are not and some are quite restrictively licensed. Most of the restrictions are around (re)distribution, so that does not apply here. Which leaves me with "I do not know" and "you probably need to ask a lawyer" and "his advice might vary from module to module and license to license". Or not and everything is easy as it is just on the user's computer. On the more technical side, you would loose an awful lot. Our better modules have paragraphing, sectioning, titles, footnotes, Strongs, morphology etc included and you would either loose that or reinvent that. From trampster at gmail.com Tue Jan 8 03:06:11 2013 From: trampster at gmail.com (Daniel Hughes) Date: Tue, 8 Jan 2013 23:06:11 +1300 Subject: [sword-devel] local cache of module text In-Reply-To: <20130108075101.213060@gmx.net> References: <20130108075101.213060@gmx.net> Message-ID: You make a compelling case, however I need do to more then just construct a GUI, I must construction fairly complete c# bindings. And therein lies the complication, because swig (or maybe me) for all it's promise appears to not be completely up to the task. Sincerely, Daniel On Tue, Jan 8, 2013 at 8:51 PM, Peter von Kaehne wrote: > > > Von: Daniel Hughes > > Am I allowed to pull the text out of the sword module once it is > installed > > (using the sword libs) and put it in my local sqlite database. > > Not a lawyer, so my advice might be of limited value. Many of our modules > are public domain and essentially you can do as you like. Many are not and > some are quite restrictively licensed. Most of the restrictions are around > (re)distribution, so that does not apply here. Which leaves me with "I do > not know" and "you probably need to ask a lawyer" and "his advice might > vary from module to module and license to license". Or not and everything > is easy as it is just on the user's computer. > > On the more technical side, you would loose an awful lot. Our better > modules have paragraphing, sectioning, titles, footnotes, Strongs, > morphology etc included and you would either loose that or reinvent that. > > From our engine you would get readily formatted HTML (or whatever else you > ask it) after application of a variety of arbitrary (or user chosen) > filters which add or remove notes, add or remove strongs, add or remove > Greek accents, Hebrew vowels and other stuff, add or remove xrefs, > transliterate, add ruby notation (for Japanese modules) etc etc. And etc. > > You would get for free all the logic to deal with different canons and > versification systems. You would get for free any future improvements to > our engine. You get indexed search with quite interesting ways of looking > at the text built in. > > For all these things you would in essence only need to construct a GUI and > interface, while in your current sqlite backend you either do not have them > or you need to re-invent them. > > Yours > > Peter > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Tue Jan 8 04:27:47 2013 From: chrislit at crosswire.org (Chris Little) Date: Tue, 08 Jan 2013 03:27:47 -0800 Subject: [sword-devel] local cache of module text In-Reply-To: <20130108075101.213060@gmx.net> References: <20130108075101.213060@gmx.net> Message-ID: <50EC02B3.8080901@crosswire.org> On 01/07/2013 11:51 PM, Peter von Kaehne wrote: > >> Von: Daniel Hughes Am I allowed to pull the >> text out of the sword module once it is installed (using the sword >> libs) and put it in my local sqlite database. > > Not a lawyer, so my advice might be of limited value. Many of our > modules are public domain and essentially you can do as you like. > Many are not and some are quite restrictively licensed. Most of the > restrictions are around (re)distribution, so that does not apply > here. Which leaves me with "I do not know" and "you probably need to > ask a lawyer" and "his advice might vary from module to module and > license to license". Or not and everything is easy as it is just on > the user's computer. Third party extraction and reformatting are naturally not things for which we negotiate rights. There are a handful of modules for which you would end up stripping encryption, meaning you're entering a whole DMCA-violation arena. And other modules are going to be a problem because you're format-shifting and our license only permits use in Sword format; we can't even convert such modules to GoBible format and distribute them though we have licenses to distribute in Sword format. The closest bit of case law I can think of is DVD CCA v. Kaleidescape. Kaleidescape built DVD-ripping jukeboxes to store DVD movies for playback on a multi-room system. They did everything possible to respect copyrights. You had to possess the DVD to rip it, but fundamentally their hardware was copying & storing DVDs on harddrives. Eight years after the DVD CCA filed its case, they're still in court trying to decide if Kaleidescape has a license that covers the machines it builds. --Chris From jhphx at cox.net Tue Jan 8 08:54:57 2013 From: jhphx at cox.net (jhphx) Date: Tue, 08 Jan 2013 08:54:57 -0700 Subject: [sword-devel] local cache of module text In-Reply-To: References: Message-ID: <50EC4151.5090304@cox.net> On 1/7/2013 6:22 PM, Daniel Hughes wrote: > ... > Am I allowed to pull the text out of the sword module once it is > installed (using the sword libs) and put it in my local sqlite > database. This would be the lest path of resistance for getting sword > module support in my application. It would also limit the amount of c# > swig bindings I will need (I have enough working to get the text but > that's it, the bindings are proving problematic.) > ... Each module could be under copyright or not. Each module could come with various licenses or not. You need to satisfy the restrictions of each module individually. This is why the development of a universal sword exporter (export any module) will not be supported. The reverse is also true. The creation of modules by importing from other non-sword formats that may be used to distribute copyrighted texts for other software packages is not universally good (or bad) and so can't be done on a universal scale. Jerry From nb at bollow.ch Tue Jan 8 11:05:40 2013 From: nb at bollow.ch (Norbert Bollow) Date: Tue, 8 Jan 2013 19:05:40 +0100 Subject: [sword-devel] local cache of module text In-Reply-To: <20130108075101.213060@gmx.net> References: <20130108075101.213060@gmx.net> Message-ID: <20130108190540.7d6da99e@quill.bollow.ch> > > Von: Daniel Hughes > > Am I allowed to pull the text out of the sword module once it is > > installed (using the sword libs) and put it in my local sqlite > > database. The legal rules regarding this kind of activity differ from country to country. Here in Switzerland, that would be allowed by law (i.e. without requiring a license from the copyright holder) provided that that database is used only for personal (in particular, not commercial) purposes, and that if you grant access to that db to anyone besides yourself, they are people in your personal circle (i.e. family, and/or friends) and they don't pay you for the privilege. Blessings and greetings, Norbert From greg.hellings at gmail.com Tue Jan 8 13:39:05 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Tue, 8 Jan 2013 14:39:05 -0600 Subject: [sword-devel] SFTP Support In-Reply-To: <50E9D0AB.7010801@crosswire.org> References: <50D7DC71.1040002@crosswire.org> <50E10268.4040505@crosswire.org> <50E9D0AB.7010801@crosswire.org> Message-ID: Thanks! I updated CMake as we talked about. The current SVN HEAD of Xiphos now has support for adding SFTP sources through its module manager. Shout-out to Karl (or whoever wrote that dialog) for making the code there very straightforward. Just adding a source with type "SFTP" in Xiphos' module manager will create the necessary entry in InstallMgr.conf and any SFTP sources that SWORD reports will act normally. Note that SWORD will silently and harmlessly ignore any InstallMgr.conf entries that are SFTPSource entries if it was compiled without SFTP support. --Greg On Sun, Jan 6, 2013 at 1:29 PM, Troy A. Griffitts wrote: > Applied. Thanks Greg, for the original contribution and for taking the time > to work through the details. > > > On 12/31/2012 03:53 PM, Greg Hellings wrote: > > Here is the updated patch adding CURLSFTPAVAILABLE support to CMake as > well as to the library code. It defaults to assuming no SFTP support > if either the curl-config executable cannot be found or if it returns > a value other than "1" from the quick detection process we have > settled on. > > Users of Windows builds through either VisualStudio or Borland will > need to figure out if curl-config is available on their systems and, > if not, come up with another way to detect and support SFTP for > clients using those builds. On Linux it is a Bash script, so it might > be adaptable to Manfred's XCode system in some way also. > > For those in the JSword world, I am sure there are SFTP Java clients > available which could be leveraged if they wanted to add support for > the same functionality to JSword applications. > > --Greg > > On Sun, Dec 30, 2012 at 9:11 PM, Troy A. Griffitts > wrote: > > OK Greg, > > I've hacked detection of CURL SFTP into the autotools build (hopefully-- it > works for me). > > I've added a new compile time define with -DCURLSFTPAVAILABLE to go along > with the existing -DCURLAVAILABLE > > If you'd like to update the sftp patch to conditionally compile support in > based on this define, that would be cool. I'll do it myself soon if you > don't have time. > > Troy > > > > On 12/28/2012 11:42 AM, Greg Hellings wrote: > > Further digging with help from our friends has revealed this nugget: > > $ curl-config --protocols > > produces a newline-delimited list of protocols that the particular > build of libcurl supports. curl-config is a shell script which can be > run on the build system and should satisfy both the requirements of > native builds and cross-compiling support. We could use this to set a > compiler macro indicating support (or not) for SFTP in the target > libcurl library. > > If someone wants to tackle that in the autotools world, I can add > detection to CMake as well. A simple command such as > $ curl-config --protocols | grep SFTP | wc -l > 1 > > in Fedora will result in a value of 1 or greater if SFTP is supported > while it should produce 0 if SFTP support is left out. An Ubuntu > system produce this output: > $ curl-config --protocols | grep SFTP | wc -l > 0 > > And it even works for cross-compiling: > $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols | > grep SFTP | wc -l > 1 > > > This appears to be our best way forward if we want to enable > compile-time enabling or disabling of this option. > > --Greg > > On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings > wrote: > > Troy, > > On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts > wrote: > > Dear Greg, > > Looking to apply this SFTP patch, could you give me some background as > to > why the check to ignore across all transports for '.' and '..'? > > Our downloading method runs recursively from the given directory until > it runs out of directory depth. FTP servers don't usually seem to > return . and .. as valid paths, and the HTTP(S) transport attempts to > parse the returned HTML page to avoid the link to the parent > directory. But whatever options are passed by cURL to the SFTP > transport resulted in it returning . and .. as paths within the > current directory. Because '.' came first in the list, the installmgr > was running through an infinite loop whenever it tried to pull data > from the server. > > I added it at the level of all transports because we don't want to > either loop infinitely on '.' or accidentally pull a whole server > recursively by following '..' to the root of the server. It might be a > server config option that permits it, but I wanted to avoid the > possibility of the InlstallMgr class getting choked up on it. > > --Greg > > Thanks, > > Troy > > > > > On 12/03/2012 04:06 PM, Greg Hellings wrote: > > The attached patch will introduce support for SFTPSource transports in > the SWORD engine, allowing a user to access remote repositories over > SFTP (which is enabled by default when a user enables SSH). > > --Greg > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dfhmch at googlemail.com Tue Jan 8 13:50:55 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 8 Jan 2013 12:50:55 -0800 (PST) Subject: [sword-devel] The SWORD Project for Windows Message-ID: <1357678255138-4651650.post@n4.nabble.com> Is *The SWORD Project for Windows* ever going to be updated? Or should I move the link from our wiki main page to http://crosswire.org/wiki/Frontends:No_longer_actively_being_developed David -- View this message in context: http://sword-dev.350566.n4.nabble.com/The-SWORD-Project-for-Windows-tp4651650.html Sent from the SWORD Dev mailing list archive at Nabble.com. From scribe at crosswire.org Tue Jan 8 15:56:45 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Tue, 08 Jan 2013 23:56:45 +0100 Subject: [sword-devel] local cache of module text In-Reply-To: References: <20130108075101.213060@gmx.net> Message-ID: <50ECA42D.1080302@crosswire.org> Daniel, Please have a look at this IDL. This is the minimum interface which I usually create when wrapping the SWORD engine. It is full featured enough to use all the features of the engine which do no require extending functionality. SWORDWeb uses this interface and our JNI bindings use this interface (Android bindings). http://crosswire.org/svn/sword/trunk/bindings/corba/swordorb.idl It is a very small set of classes and methods on those classes and shouldn't be hard to created C# bindings for these. Hope this is useful, Troy On 01/08/2013 11:06 AM, Daniel Hughes wrote: > You make a compelling case, however I need do to more then just > construct a GUI, I must construction fairly complete c# bindings. And > therein lies the complication, because swig (or maybe me) for all it's > promise appears to not be completely up to the task. > > Sincerely, > Daniel > > > On Tue, Jan 8, 2013 at 8:51 PM, Peter von Kaehne > wrote: > > > > Von: Daniel Hughes > > > Am I allowed to pull the text out of the sword module once it is > installed > > (using the sword libs) and put it in my local sqlite database. > > Not a lawyer, so my advice might be of limited value. Many of our > modules are public domain and essentially you can do as you like. > Many are not and some are quite restrictively licensed. Most of > the restrictions are around (re)distribution, so that does not > apply here. Which leaves me with "I do not know" and "you probably > need to ask a lawyer" and "his advice might vary from module to > module and license to license". Or not and everything is easy as > it is just on the user's computer. > > On the more technical side, you would loose an awful lot. Our > better modules have paragraphing, sectioning, titles, footnotes, > Strongs, morphology etc included and you would either loose that > or reinvent that. > > >From our engine you would get readily formatted HTML (or whatever > else you ask it) after application of a variety of arbitrary (or > user chosen) filters which add or remove notes, add or remove > strongs, add or remove Greek accents, Hebrew vowels and other > stuff, add or remove xrefs, transliterate, add ruby notation (for > Japanese modules) etc etc. And etc. > > You would get for free all the logic to deal with different canons > and versification systems. You would get for free any future > improvements to our engine. You get indexed search with quite > interesting ways of looking at the text built in. > > For all these things you would in essence only need to construct a > GUI and interface, while in your current sqlite backend you either > do not have them or you need to re-invent them. > > Yours > > Peter > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampster at gmail.com Tue Jan 8 16:38:13 2013 From: trampster at gmail.com (Daniel Hughes) Date: Wed, 9 Jan 2013 12:38:13 +1300 Subject: [sword-devel] local cache of module text In-Reply-To: <50ECA42D.1080302@crosswire.org> References: <20130108075101.213060@gmx.net> <50ECA42D.1080302@crosswire.org> Message-ID: Thanks Troy, that interface looks manageable. Does it support creating and using lucene indexes? I need that of as you type searching. Cheers, Daniel On Wed, Jan 9, 2013 at 11:56 AM, Troy A. Griffitts wrote: > Daniel, > > Please have a look at this IDL. This is the minimum interface which I > usually create when wrapping the SWORD engine. It is full featured enough > to use all the features of the engine which do no require extending > functionality. SWORDWeb uses this interface and our JNI bindings use this > interface (Android bindings). > > http://crosswire.org/svn/sword/trunk/bindings/corba/swordorb.idl > > It is a very small set of classes and methods on those classes and > shouldn't be hard to created C# bindings for these. > > Hope this is useful, > > Troy > > > > > On 01/08/2013 11:06 AM, Daniel Hughes wrote: > > You make a compelling case, however I need do to more then just construct > a GUI, I must construction fairly complete c# bindings. And therein lies > the complication, because swig (or maybe me) for all it's promise appears > to not be completely up to the task. > > Sincerely, > Daniel > > > On Tue, Jan 8, 2013 at 8:51 PM, Peter von Kaehne wrote: > >> >> > Von: Daniel Hughes >> > Am I allowed to pull the text out of the sword module once it is >> installed >> > (using the sword libs) and put it in my local sqlite database. >> >> Not a lawyer, so my advice might be of limited value. Many of our >> modules are public domain and essentially you can do as you like. Many are >> not and some are quite restrictively licensed. Most of the restrictions are >> around (re)distribution, so that does not apply here. Which leaves me with >> "I do not know" and "you probably need to ask a lawyer" and "his advice >> might vary from module to module and license to license". Or not and >> everything is easy as it is just on the user's computer. >> >> On the more technical side, you would loose an awful lot. Our better >> modules have paragraphing, sectioning, titles, footnotes, Strongs, >> morphology etc included and you would either loose that or reinvent that. >> >> >From our engine you would get readily formatted HTML (or whatever else >> you ask it) after application of a variety of arbitrary (or user chosen) >> filters which add or remove notes, add or remove strongs, add or remove >> Greek accents, Hebrew vowels and other stuff, add or remove xrefs, >> transliterate, add ruby notation (for Japanese modules) etc etc. And etc. >> >> You would get for free all the logic to deal with different canons and >> versification systems. You would get for free any future improvements to >> our engine. You get indexed search with quite interesting ways of looking >> at the text built in. >> >> For all these things you would in essence only need to construct a GUI >> and interface, while in your current sqlite backend you either do not have >> them or you need to re-invent them. >> >> Yours >> >> Peter >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 9 19:54:35 2013 From: thulester at gmail.com (Andrew Thule) Date: Wed, 9 Jan 2013 21:54:35 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: <50E84537.1000608@gmail.com> References: <50E84537.1000608@gmail.com> Message-ID: Are you seeing a problem with $SWORDSRC/src/utilfuns/swversion.cpp not finding config.h? ./src/sword/utilfuns/swversion.cpp:18:20: fatal error: config.h: No such file or directory ~A On Saturday, January 5, 2013, Ben wrote: > Hey Andrew, > > Cmake is a replacement for autotools/configure - it still uses make. Cmake > isn't related to python. > > The normal sequence with cmake is: > cmake > make > make install > > The normal sequence otherwise is: > ./configure > make > make install > > So cmake is just another way of setting up the Makefiles and build process. > > -Ben > > On 01/04/2013 05:42 PM, Andrew Thule wrote: > >> I'm curious, why do people seem to prefer cmake to make? Is that a >> python thing? >> >> ~A >> >> >> On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings > > wrote: >> >> On Sat, Dec 22, 2012 at 12:51 PM, > > wrote: >> > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings >> > wrote: >> >>> On Tue, Dec 18, 2012 at 9:27 PM, > > wrote: >> >>> Here's a patch that helps some with osistest. I still get the >> >>> following error when I run osistest, though: >> >>> UTF8Transliterator: ICU: no resource index to load >> >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >> >> >> >> This is because it's not finding the locales or some such. I very >> >> frequently get it, mainly when running from an uninstalled SWORD >> >> instance but it happens other times even on install. >> >> >> >> I'll see about applying these patches. >> > >> > Here's patch that I think helps with the ICU support. It finds the >> > genrb command, and then also sets the ICU_VERSION variable, like >> the >> > configure build system does. (The osis test still fails, but it >> > doesn't have the UTF8Transliterator error.) >> >> Your patch was on the right path but used icu-config which is horridly >> broken in native Windows builds (it's a Bash script) or in cross-build >> environments from Linux (it explodes looking for a .so library when it >> should look for a .dll). >> >> I have substituted using CMake's built-in pkg-config functions to pull >> out the modversion variable of libicuuc, which is one of the few that >> we actually link directly against. >> >> I wish I could tell you why that fixes the issue, but it does. Thank >> you much, because that has been bugging me for a long time. The fix >> should be in the SVN HEAD now. >> >> --Greg >> >> > >> > -Ben >> > >> > ______________________________**_________________ >> > sword-devel mailing list: sword-devel at crosswire.org >> >> > http://www.crosswire.org/**mailman/listinfo/sword-devel >> > Instructions to unsubscribe/change your settings at above page >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cricketc at gmail.com Wed Jan 9 20:07:19 2013 From: cricketc at gmail.com (Ben) Date: Wed, 09 Jan 2013 22:07:19 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: References: <50E84537.1000608@gmail.com> Message-ID: <50EE3067.5050509@gmail.com> I haven't been seeing that. Is that when you run cmake? What options are you using? On 01/09/2013 09:54 PM, Andrew Thule wrote: > Are you seeing a problem with $SWORDSRC/src/utilfuns/swversion.cpp not > finding config.h? > ./src/sword/utilfuns/swversion.cpp:18:20: fatal error: config.h: No such > file or directory > > ~A > > On Saturday, January 5, 2013, Ben wrote: > > Hey Andrew, > > Cmake is a replacement for autotools/configure - it still uses make. > Cmake isn't related to python. > > The normal sequence with cmake is: > cmake > make > make install > > The normal sequence otherwise is: > ./configure > make > make install > > So cmake is just another way of setting up the Makefiles and build > process. > > -Ben > > On 01/04/2013 05:42 PM, Andrew Thule wrote: > > I'm curious, why do people seem to prefer cmake to make? Is that a > python thing? > > ~A > > > On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings > > wrote: > > On Sat, Dec 22, 2012 at 12:51 PM, > wrote: > > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings > > > wrote: > >>> On Tue, Dec 18, 2012 at 9:27 PM, > wrote: > >>> Here's a patch that helps some with osistest. I still > get the > >>> following error when I run osistest, though: > >>> UTF8Transliterator: ICU: no resource index to load > >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR > >> > >> This is because it's not finding the locales or some > such. I very > >> frequently get it, mainly when running from an > uninstalled SWORD > >> instance but it happens other times even on install. > >> > >> I'll see about applying these patches. > > > > Here's patch that I think helps with the ICU support. It > finds the > > genrb command, and then also sets the ICU_VERSION > variable, like the > > configure build system does. (The osis test still fails, > but it > > doesn't have the UTF8Transliterator error.) > > Your patch was on the right path but used icu-config which > is horridly > broken in native Windows builds (it's a Bash script) or in > cross-build > environments from Linux (it explodes looking for a .so > library when it > should look for a .dll). > > I have substituted using CMake's built-in pkg-config > functions to pull > out the modversion variable of libicuuc, which is one of > the few that > we actually link directly against. > > I wish I could tell you why that fixes the issue, but it > does. Thank > you much, because that has been bugging me for a long time. > The fix > should be in the SVN HEAD now. > > --Greg > > > > > -Ben > > > > _________________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > > http://www.crosswire.org/__mailman/listinfo/sword-devel > > > Instructions to unsubscribe/change your settings at > above page > > _________________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/__mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > _________________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/__mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > _________________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/__mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From 5001 at hotmail.com Wed Jan 9 20:12:52 2013 From: 5001 at hotmail.com (Pola Edward) Date: Thu, 10 Jan 2013 05:12:52 +0200 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: Message-ID: Could anyone help ?! From: 5001 at hotmail.com To: sword-devel at crosswire.org Date: Mon, 7 Jan 2013 22:02:48 +0200 Subject: [sword-devel] Complete Osis Commentary Example Hi, Sorry for sending this to the wrong list, but this list is more active than osis-users list , My previous post in osis-users list didn't got attention and i got just 2 replies and no one replied after my last reply . The problem still exists and I've made many many trials, trying to get it to work the wiki doesn't contain a complete osis commentary example like bibles section the following is a complete osis structure i tried, it appears in xiphos and BPBible, but no effect for titles, bold and underline tags, all texts appear the same in the output . in programs like Bible Time, I see xml structure instead of normal texts Please send me a Complete Osis Commentary Example, so I can follow it
????? ????? ????? ????? ???? Bible.FrTadros Bible.KJV Bible.KJV
This is a title, and supposed to be bold and underlined

blah blah blah blah blah blah Please see James 1:19

_______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 9 22:23:34 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 10 Jan 2013 00:23:34 -0500 Subject: [sword-devel] CMake ICU (was Re: cmake python) In-Reply-To: <50EE3067.5050509@gmail.com> References: <50E84537.1000608@gmail.com> <50EE3067.5050509@gmail.com> Message-ID: No options. Just cmake ../sword On Wednesday, January 9, 2013, Ben wrote: > I haven't been seeing that. Is that when you run cmake? What options are > you using? > > On 01/09/2013 09:54 PM, Andrew Thule wrote: > >> Are you seeing a problem with $SWORDSRC/src/utilfuns/**swversion.cpp not >> finding config.h? >> ./src/sword/utilfuns/**swversion.cpp:18:20: fatal error: config.h: No >> such >> file or directory >> >> ~A >> >> On Saturday, January 5, 2013, Ben wrote: >> >> Hey Andrew, >> >> Cmake is a replacement for autotools/configure - it still uses make. >> Cmake isn't related to python. >> >> The normal sequence with cmake is: >> cmake >> make >> make install >> >> The normal sequence otherwise is: >> ./configure >> make >> make install >> >> So cmake is just another way of setting up the Makefiles and build >> process. >> >> -Ben >> >> On 01/04/2013 05:42 PM, Andrew Thule wrote: >> >> I'm curious, why do people seem to prefer cmake to make? Is that >> a >> python thing? >> >> ~A >> >> >> On Fri, Jan 4, 2013 at 5:09 PM, Greg Hellings >> > > wrote: >> >> On Sat, Dec 22, 2012 at 12:51 PM, > > wrote: >> > On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings >> > >> wrote: >> >>> On Tue, Dec 18, 2012 at 9:27 PM, > > wrote: >> >>> Here's a patch that helps some with osistest. I still >> get the >> >>> following error when I run osistest, though: >> >>> UTF8Transliterator: ICU: no resource index to load >> >>> UTF8Transliterator: ICU: status U_MISSING_RESOURCE_ERROR >> >> >> >> This is because it's not finding the locales or some >> such. I very >> >> frequently get it, mainly when running from an >> uninstalled SWORD >> >> instance but it happens other times even on install. >> >> >> >> I'll see about applying these patches. >> > >> > Here's patch that I think helps with the ICU support. It >> finds the >> > genrb command, and then also sets the ICU_VERSION >> variable, like the >> > configure build system does. (The osis test still fails, >> but it >> > doesn't have the UTF8Transliterator error.) >> >> Your patch was on the right path but used icu-config which >> is horridly >> broken in native Windows builds (it's a Bash script) or in >> cross-build >> environments from Linux (it explodes looking for a .so >> library when it >> should look for a .dll). >> >> I have substituted using CMake's built-in pkg-config >> functions to pull >> out the modversion variable of libicuuc, which is one of >> the few that >> we actually link directly against. >> >> I wish I could tell you why that fixes the issue, but it >> does. Thank >> you much, because that has been bugging me for a long time. >> The fix >> should be in the SVN HEAD now. >> >> --Greg >> >> > >> > -Ben >> > >> > ______________________________**___________________ >> > sword-devel mailing list: sword-devel at crosswire.org >> >> > http://www.crosswire.org/__**mailman/listinfo/sword-devel >> >> > >> > Instructions to unsubscribe/change your settings at >> above page >> >> ______________________________**___________________ >> sword-devel mailing list: sword-devel at crosswire.org >> >> http://www.crosswire.org/__**mailman/listinfo/sword-devel >> >> > >> Instructions to unsubscribe/change your settings at above >> page >> >> >> >> >> ______________________________**___________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/__**mailman/listinfo/sword-devel >> >> > >> Instructions to unsubscribe/change your settings at above page >> >> >> >> ______________________________**___________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/__**mailman/listinfo/sword-devel >> >> > >> Instructions to unsubscribe/change your settings at above page >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Wed Jan 9 22:24:16 2013 From: dmsmith at crosswire.org (DM Smith) Date: Thu, 10 Jan 2013 00:24:16 -0500 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: Message-ID: <48E9632D-6232-4945-BCA7-20490121BEDE@crosswire.org> I hope to as soon as I get some time. The document that you have below looks correct. I'm wondering if there is a problem with how it is stored as a module and how the SWORD engine handles it. If it shows correctly in BibleDesktop (or another JSword front-end) then the problem is not in your encoding. In Him, DM On Jan 9, 2013, at 10:12 PM, Pola Edward <5001 at hotmail.com> wrote: > Could anyone help ?! > > From: 5001 at hotmail.com > To: sword-devel at crosswire.org > Date: Mon, 7 Jan 2013 22:02:48 +0200 > Subject: [sword-devel] Complete Osis Commentary Example > > Hi, > Sorry for sending this to the wrong list, but this list is more active than osis-users list , My previous post in osis-users list didn't got attention and i got just 2 replies and no one replied after my last reply . > > The problem still exists and I've made many many trials, trying to get it to work > the wiki doesn't contain a complete osis commentary example like bibles section > > the following is a complete osis structure i tried, it appears in xiphos and BPBible, but no effect for titles, bold and underline tags, all texts appear the same in the output . > in programs like Bible Time, I see xml structure instead of normal texts > > Please send me a Complete Osis Commentary Example, so I can follow it > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > >
> > ????? ????? ????? ????? ???? > Bible.FrTadros > Bible.KJV > > > Bible.KJV > >
>
>
> >
> This is a title, and supposed to be bold and underlined >

> > blah blah blah > blah blah blah > Please see James 1:19 >

>
>
>
>
>
>
> > _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 9 22:25:52 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 10 Jan 2013 00:25:52 -0500 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: Message-ID: Pola, I was looking at it to recreate the problem. I created a test module with the snippet you provided, and was having issues of my own, so I don't yet know what the issue is, but I'm still looking ... ~A On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com> wrote: > Could anyone help ?! > > ------------------------------ > From: 5001 at hotmail.com > To: sword-devel at crosswire.org 'sword-devel at crosswire.org');> > Date: Mon, 7 Jan 2013 22:02:48 +0200 > Subject: [sword-devel] Complete Osis Commentary Example > > Hi, > Sorry for sending this to the wrong list, but this list is more active > than osis-users list , My previous post in osis-users list didn't got > attention and i got just 2 replies and no one replied after my last reply . > > The problem still exists and I've made many many trials, trying to get it > to work > the wiki doesn't contain a complete osis commentary example like bibles > section > > the following is a complete osis structure i tried, it appears in xiphos > and BPBible, but no effect for titles, bold and underline tags, all texts > appear the same in the output . > in programs like Bible Time, I see xml structure instead of normal texts > > Please send me a Complete Osis Commentary Example, so I can follow it > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > xml:lang="en"> >
> > ????? ????? ????? ????? ???? > Bible.FrTadros > Bible.KJV > > > Bible.KJV > >
>
>
> >
type="section"> > This is a title, > and supposed to be bold and underlined >

> > blah blah blah > blah blah blah > Please see James 1:19 >

>
>
>
>
>
>
> > _______________________________________________ sword-devel mailing list: > sword-devel at crosswire.org 'sword-devel at crosswire.org');> > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 9 22:27:40 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 10 Jan 2013 00:27:40 -0500 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: Message-ID: If I have a recommendation it is to download the KJV.zip and use the OSIS examples in their as templates ... ~A On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com> wrote: > Could anyone help ?! > > ------------------------------ > From: 5001 at hotmail.com > To: sword-devel at crosswire.org 'sword-devel at crosswire.org');> > Date: Mon, 7 Jan 2013 22:02:48 +0200 > Subject: [sword-devel] Complete Osis Commentary Example > > Hi, > Sorry for sending this to the wrong list, but this list is more active > than osis-users list , My previous post in osis-users list didn't got > attention and i got just 2 replies and no one replied after my last reply . > > The problem still exists and I've made many many trials, trying to get it > to work > the wiki doesn't contain a complete osis commentary example like bibles > section > > the following is a complete osis structure i tried, it appears in xiphos > and BPBible, but no effect for titles, bold and underline tags, all texts > appear the same in the output . > in programs like Bible Time, I see xml structure instead of normal texts > > Please send me a Complete Osis Commentary Example, so I can follow it > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > xml:lang="en"> >
> > ????? ????? ????? ????? ???? > Bible.FrTadros > Bible.KJV > > > Bible.KJV > >
>
>
> >
type="section"> > This is a title, > and supposed to be bold and underlined >

> > blah blah blah > blah blah blah > Please see James 1:19 >

>
>
>
>
>
>
> > _______________________________________________ sword-devel mailing list: > sword-devel at crosswire.org 'sword-devel at crosswire.org');> > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yudahsshadow at gmx.com Thu Jan 10 16:27:46 2013 From: yudahsshadow at gmx.com (David Blue) Date: Thu, 10 Jan 2013 18:27:46 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> Message-ID: <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> Based on the*.crosswire.org rule I would say the best option when and if mirrors are needed is to have some sort of round robin dns that picks a mirror from an internal list the way microsoft.com or my Linux distro does download.opensuse.org for it's package repos. Sorry for the top post' Nic Carter wrote: > >Sent from my phone, hence this email may be short... > >On 08/01/2013, at 8:51, Andrew Thule wrote: > >> >> As long as Crosswire has policies in place govererning official >mirrors there should no no worries mirrors are out of sync, in which >case preferred mirror selection can be left to the user, and indeed >mirror checking behaviour configurable. > >Yup, policy is no mirrors at this point in time. >It is thought that there _may_ be room in the future for some, but >these will be done from a *.crosswire.org domain so as to satisfy >copyright requirements. > >Easy :) > >Thanks for your thoughts & I'm glad we can now put this discussion to >rest. :) > >_______________________________________________ >sword-devel mailing list: sword-devel at crosswire.org >http://www.crosswire.org/mailman/listinfo/sword-devel >Instructions to unsubscribe/change your settings at above page -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5001 at hotmail.com Fri Jan 11 13:02:27 2013 From: 5001 at hotmail.com (Pola Edward) Date: Fri, 11 Jan 2013 22:02:27 +0200 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: , , Message-ID: Thanks for the reply, Attached the images using your markup, no effect in 3 programs You can see screenshots here http://depositfiles.com/files/36011rgm3 I'm thinking in making the commentaries in intermediate markup format, so Data entry group can start ASAP, and I'll convert it later to any format Note: Xiphos, displayed the ThML markup inside OSIS XML correctly in previous trials, but other Apps didn't display it the same and just ignored it Pola Date: Thu, 10 Jan 2013 00:27:40 -0500 From: thulester at gmail.com To: sword-devel at crosswire.org Subject: Re: [sword-devel] Complete Osis Commentary Example If I have a recommendation it is to download the KJV.zip and use the OSIS examples in their as templates ...~A On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com> wrote: Could anyone help ?! From: 5001 at hotmail.com To: sword-devel at crosswire.org Date: Mon, 7 Jan 2013 22:02:48 +0200 Subject: [sword-devel] Complete Osis Commentary Example Hi, Sorry for sending this to the wrong list, but this list is more active than osis-users list , My previous post in osis-users list didn't got attention and i got just 2 replies and no one replied after my last reply . The problem still exists and I've made many many trials, trying to get it to work the wiki doesn't contain a complete osis commentary example like bibles section the following is a complete osis structure i tried, it appears in xiphos and BPBible, but no effect for titles, bold and underline tags, all texts appear the same in the output . in programs like Bible Time, I see xml structure instead of normal texts Please send me a Complete Osis Commentary Example, so I can follow it
????? ????? ????? ????? ???? Bible.FrTadros Bible.KJV Bible.KJV
This is a title, and supposed to be bold and underlined

blah blah blah blah blah blah Please see James 1:19

_______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 11 16:40:46 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 11 Jan 2013 18:40:46 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> Message-ID: Ultimately, the issue is about licensing rights on modules, which appears to be a very touchy subject around here. I suspect this is so because without actual licenses, which are essentially legal agreements (I'm not talking about .conf files which are not legal agreements), its pretty much impossible to claims legal rights and restrictions exist without proof. As people like to point out, Copyright resides with the Copyright owner. For a third party to 'claim' the right to distribute text they are not the Copyright owner of, explicit license had to have been given (a legally binding agreement). What this means for mirrors is this: Anyone can run an FTP service. Anyone can call the directories anything they want in said FTP service. What people place in their FTP servers is where the controversy starts. Others, (not me) have already pointed out that Crosswire doesn't (and can't) control modules once they leave Crosswire's repo. This means Crosswire, as the non-owner, has nothing to say about modules elsewhere. Crosswire tries to asserts legal right over some modules however. There are only two ways under copyright law, Crosswire can exercise rights over copyrighted work: 1. Direct Ownership. Para 106 of of US Copyright law says that the Copyright owner has exclusive rights over their wok, so Crosswire would have to prove it were the Copyright Owner; or 2. Transfer and Licensing of rights. The Owner can transfer rights through formal agreement specificaly expressing those rights (and ultimately granted through a written instrument, signed by the grantor). This is a license, or possibly exclusive license. Under US law, exclusive licenses must be recorded in the US Copyright office or exclusive license is not valid (Para 408) If Crosswire has been exclusively license then, it may establish a rule only certain repositories may distribute modules, but the terms of this license (with the Copyright owner) are not secret (and indeed a matter of public record). If Crosswire has not been exclusively licensed however, Crosswire has no legal right to prohibit others from distributing modules it freely distributes in a non-commercial manner (however much it rants and maligns others). That means for there to be a *.crosswire.org 'rule' Crosswire's exclusive license must be registered and public, or it lacks authority to assert rights over text it doesn't own. People should not get upset when this rule is not followed then. (Don't shoot the messenger because you don't like the law) ~A On Thursday, January 10, 2013, David Blue wrote: > Based on the*.crosswire.org rule I would say the best option when and if > mirrors are needed is to have some sort of round robin dns that picks a > mirror from an internal list the way microsoft.com or my Linux distro > does download.opensuse.org for it's package repos. Sorry for the top post' > > Nic Carter wrote: >> >> >> Sent from my phone, hence this email may be short... >> >> On 08/01/2013, at 8:51, Andrew Thule wrote: >> >> >> >> As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. >> >> >> >> Yup, policy is no mirrors at this point in time. >> It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. >> >> >> Easy :) >> >> Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) >> >> ------------------------------ >> >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niccarter at mac.com Fri Jan 11 16:57:10 2013 From: niccarter at mac.com (Nic Carter) Date: Sat, 12 Jan 2013 10:57:10 +1100 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> Message-ID: <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> Hi Andrew, You completely miss the point! CrossWire has the right to distribute certain modules. In order to satisfy our legal agreement with the copyright holders we can can only distribute from "CrossWire". We do not own the copyright, we have to abide by the same rules as anyone else. We are simply in the awesome position of having been granted permission. Also, when I say "we", I am meaning CrossWire. However, even though I am a volunteer as part of CrossWire, that does not give me the right to distribute anything. Distribution has to be simply by CrossWire and the most proper way to satisfy those legal agreements is to distribute from an official CrossWire domain so as to strive the hardest to remain above board. :) I am now lead to believe that what certain other people have said here is correct and that you do not understand any of this legal mumbo jumbo at all, and hence I think you should cease trying to educate others and instead simply cede to Troy and if you wish to help with this project, follow his lead, asking him what he wants of you. Thank you. Nic... :) On 12/01/2013, at 10:40, Andrew Thule wrote: > Ultimately, the issue is about licensing rights on modules, which appears to be a very touchy subject around here. I suspect this is so because without actual licenses, which are essentially legal agreements (I'm not talking about .conf files which are not legal agreements), its pretty much impossible to claims legal rights and restrictions exist without proof. > > As people like to point out, Copyright resides with the Copyright owner. For a third party to 'claim' the right to distribute text they are not the Copyright owner of, explicit license had to have been given (a legally binding agreement). What this means for mirrors is this: > > Anyone can run an FTP service. > Anyone can call the directories anything they want in said FTP service. > What people place in their FTP servers is where the controversy starts. > > Others, (not me) have already pointed out that Crosswire doesn't (and can't) control modules once they leave Crosswire's repo. This means Crosswire, as the non-owner, has nothing to say about modules elsewhere. Crosswire tries to asserts legal right over some modules however. There are only two ways under copyright law, Crosswire can exercise rights over copyrighted work: > > 1. Direct Ownership. Para 106 of of US Copyright law says that the Copyright owner has exclusive rights over their wok, so Crosswire would have to prove it were the Copyright Owner; or > 2. Transfer and Licensing of rights. The Owner can transfer rights through formal agreement specificaly expressing those rights (and ultimately granted through a written instrument, signed by the grantor). This is a license, or possibly exclusive license. Under US law, exclusive licenses must be recorded in the US Copyright office or exclusive license is not valid (Para 408) > > If Crosswire has been exclusively license then, it may establish a rule only certain repositories may distribute modules, but the terms of this license (with the Copyright owner) are not secret (and indeed a matter of public record). > If Crosswire has not been exclusively licensed however, Crosswire has no legal right to prohibit others from distributing modules it freely distributes in a non-commercial manner (however much it rants and maligns others). > > That means for there to be a *.crosswire.org 'rule' Crosswire's exclusive license must be registered and public, or it lacks authority to assert rights over text it doesn't own. People should not get upset when this rule is not followed then. > > (Don't shoot the messenger because you don't like the law) > > ~A > > On Thursday, January 10, 2013, David Blue wrote: >> Based on the*.crosswire.org rule I would say the best option when and if mirrors are needed is to have some sort of round robin dns that picks a mirror from an internal list the way microsoft.com or my Linux distro does download.opensuse.org for it's package repos. Sorry for the top post' >> >> Nic Carter wrote: >>> >>> >>> Sent from my phone, hence this email may be short... >>> >>> On 08/01/2013, at 8:51, Andrew Thule wrote: >>> >>> >>> >>> >>> >>>> As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. >>> >>> >>> >>> >>> Yup, policy is no mirrors at this point in time. >>> It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. >>> >>> >>> >>> >>> Easy :) >>> >>> Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) >>> >>> >>> sword-devel mailing list: sword-devel at crosswire.org >>> >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> -- >> Sent from my Android phone with K-9 Mail. Please excuse my brevity. > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 11 16:59:31 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 11 Jan 2013 18:59:31 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> Message-ID: Oh and to be clear I'm happy (and morally obligated) to honour the law. If I see evidence Crosswire holds exclusive license to control the distribution of some modules, I will honour that license. However, if no such legal restrictions apply, I am bound by a greater commission and intend to distribute all of the modules I'm legally able to do so. I provide this proxy service for some who are not able to make it to Crosswire directly safely (and are technically prohibited from using an onion router (tor network). Without legal authority to claim exclusive rights, it is hypocrisy to freely and publicaly distribute text one doesn't own, non-commercially while denying others the same right. It is kind of like tithing dill and mint while ignoring weightier matters of law. One must possess rights before one denies others them. ~A On Thursday, January 10, 2013, David Blue wrote: > Based on the*.crosswire.org rule I would say the best option when and if > mirrors are needed is to have some sort of round robin dns that picks a > mirror from an internal list the way microsoft.com or my Linux distro > does download.opensuse.org for it's package repos. Sorry for the top post' > > Nic Carter 'niccarter at mac.com');>> wrote: >> >> >> Sent from my phone, hence this email may be short... >> >> On 08/01/2013, at 8:51, Andrew Thule > wrote: >> >> >> As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. >> >> >> Yup, policy is no mirrors at this point in time. >> It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. >> >> Easy :) >> >> Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) >> >> ------------------------------ >> >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 11 17:08:10 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 11 Jan 2013 19:08:10 -0500 Subject: [sword-devel] CrossWire mirroring In-Reply-To: <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> Message-ID: Nic, no I didn't miss the point. You are claiming this privelge is exclusive. If so, the terms of this agreement must be both registered and public. Anyone can claim anything they want about what they are able to do, and what others are not able to do, but these claims are only true if the terms of the law is met. As long as Crosswire is engaged in the public non-commercial distribution of modules, and refused to prove its right to do this is exclusive, it should accept is has no ability to control them once they've left Crosswire. ~A On Friday, January 11, 2013, Nic Carter wrote: > Hi Andrew, > > You completely miss the point! > > CrossWire has the right to distribute certain modules. In order to satisfy > our legal agreement with the copyright holders we can can only distribute > from "CrossWire". We do not own the copyright, we have to abide by the same > rules as anyone else. We are simply in the awesome position of having been > granted permission. > > Also, when I say "we", I am meaning CrossWire. However, even though I am a > volunteer as part of CrossWire, that does not give me the right to > distribute anything. Distribution has to be simply by CrossWire and the > most proper way to satisfy those legal agreements is to distribute from an > official CrossWire domain so as to strive the hardest to remain above > board. :) > > I am now lead to believe that what certain other people have said here is > correct and that you do not understand any of this legal mumbo jumbo at > all, and hence I think you should cease trying to educate others and > instead simply cede to Troy and if you wish to help with this project, > follow his lead, asking him what he wants of you. > > Thank you. > > Nic... :) > > On 12/01/2013, at 10:40, Andrew Thule > > wrote: > > Ultimately, the issue is about licensing rights on modules, which appears > to be a very touchy subject around here. I suspect this is so because > without actual licenses, which are essentially legal agreements (I'm not > talking about .conf files which are not legal agreements), its pretty much > impossible to claims legal rights and restrictions exist without proof. > > As people like to point out, Copyright resides with the Copyright owner. > For a third party to 'claim' the right to distribute text they are not the > Copyright owner of, explicit license had to have been given (a legally > binding agreement). What this means for mirrors is this: > > Anyone can run an FTP service. > Anyone can call the directories anything they want in said FTP service. > What people place in their FTP servers is where the controversy starts. > > Others, (not me) have already pointed out that Crosswire doesn't (and > can't) control modules once they leave Crosswire's repo. This means > Crosswire, as the non-owner, has nothing to say about modules elsewhere. > Crosswire tries to asserts legal right over some modules however. There > are only two ways under copyright law, Crosswire can exercise rights over > copyrighted work: > > 1. Direct Ownership. Para 106 of of US Copyright law says that > the Copyright owner has exclusive rights over their wok, so Crosswire would > have to prove it were the Copyright Owner; or > 2. Transfer and Licensing of rights. The Owner can transfer rights through > formal agreement specificaly expressing those rights (and ultimately > granted through a written instrument, signed by the grantor). This is > a license, or possibly exclusive license. Under US law, exclusive > licenses must be recorded in the US Copyright office or exclusive license > is not valid (Para 408) > > If Crosswire has been exclusively license then, it may establish a rule > only certain repositories may distribute modules, but the terms of this > license (with the Copyright owner) are not secret (and indeed a matter of > public record). > If Crosswire has not been exclusively licensed however, Crosswire has no > legal right to prohibit others from distributing modules it freely > distributes in a non-commercial manner (however much it rants and maligns > others). > > That means for there to be a *.crosswire.org 'rule' Crosswire's exclusive > license must be registered and public, or it lacks authority to assert > rights over text it doesn't own. People should not get upset when this > rule is not followed then. > > (Don't shoot the messenger because you don't like the law) > > ~A > > On Thursday, January 10, 2013, David Blue wrote: > > Based on the*.crosswire.org rule I would say the best option when and if > mirrors are needed is to have some sort of round robin dns that picks a > mirror from an internal list the way microsoft.com or my Linux distro > does download.opensuse.org for it's package repos. Sorry for the top post' > > Nic Carter wrote: > > > Sent from my phone, hence this email may be short... > > On 08/01/2013, at 8:51, Andrew Thule wrote: > > > > > As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. > > > > > Yup, policy is no mirrors at this point in time. > It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. > > > > Easy :) > > Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) > > ------------------------------ > > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org 'cvml', 'sword-devel at crosswire.org');> > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niccarter at mac.com Fri Jan 11 18:15:37 2013 From: niccarter at mac.com (Nic Carter) Date: Sat, 12 Jan 2013 12:15:37 +1100 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> Message-ID: <01A43984-C19B-4EFD-AB14-A20384C6CD62@mac.com> - There is no "exclusive" agreement. (You can access the ESV from BibleGateway, for example.) - If we are challenged by a copyright holder about our rights to distribute their content, we then take that up with them. (This happened with the ESV a few years ago, when the new guy in charge of that sort of stuff at Crossway didn't know about our agreement. This specifically affected our distribution via iOS, and we agreed to manually disable the ability to download the ESV on iOS until it was sorted out. The copyright holder challenged us. We cleared it up with them.) - If you decide that you don't trust that CrossWire has an appropriate agreement with the copyright holders, you then MUST go with what you DO know, which is to look at the rights you have from the copyright holder yourself. (So, this links with those URLs you linked to a few days ago from the copyright holder's websites, the generic licences. If you think CrossWire is lying and has no rights, you then cannot legally use any of the "copyrighted" material you can get from crosswire.org) You seem to have 2 choices. Either accept that what Troy has said before, and that the above is true, or walk away from here and look for other projects to be involved with. The material that is copyrighted that is available from crosswire.org is not available for you to redistribute. As you believe that CrossWire has stolen all that material, it would be highly illegal for you to further redistribute that stolen material. [of course, that material is NOT stolen, and many people have spent hours and days and weeks and years slowly negotiating the rights to distribute it from crosswire.org for individuals to use for personal use only] I'm done. Take the above or leave it. Accept what you have been told or decide CrossWire is an organisation of thieves. [It's not.] Either way, there is nothing to say that you have the right to further distribute modules. I'm going to be sad to see you go, but I believe that is the decision you are leaning towards, as you do not trust Troy. :( On 12/01/2013, at 11:08, Andrew Thule wrote: > Nic, no I didn't miss the point. > > You are claiming this privelge is exclusive. If so, the terms of this agreement must be both registered and public. Anyone can claim anything they want about what they are able to do, and what others are not able to do, but these claims are only true if the terms of the law is met. > > As long as Crosswire is engaged in the public non-commercial distribution of modules, and refused to prove its right to do this is exclusive, it should accept is has no ability to control them once they've left Crosswire. > > ~A > > On Friday, January 11, 2013, Nic Carter wrote: >> Hi Andrew, >> >> You completely miss the point! >> >> CrossWire has the right to distribute certain modules. In order to satisfy our legal agreement with the copyright holders we can can only distribute from "CrossWire". We do not own the copyright, we have to abide by the same rules as anyone else. We are simply in the awesome position of having been granted permission. >> >> Also, when I say "we", I am meaning CrossWire. However, even though I am a volunteer as part of CrossWire, that does not give me the right to distribute anything. Distribution has to be simply by CrossWire and the most proper way to satisfy those legal agreements is to distribute from an official CrossWire domain so as to strive the hardest to remain above board. :) >> >> I am now lead to believe that what certain other people have said here is correct and that you do not understand any of this legal mumbo jumbo at all, and hence I think you should cease trying to educate others and instead simply cede to Troy and if you wish to help with this project, follow his lead, asking him what he wants of you. >> >> Thank you. >> >> Nic... :) >> >> On 12/01/2013, at 10:40, Andrew Thule wrote: >> >>> Ultimately, the issue is about licensing rights on modules, which appears to be a very touchy subject around here. I suspect this is so because without actual licenses, which are essentially legal agreements (I'm not talking about .conf files which are not legal agreements), its pretty much impossible to claims legal rights and restrictions exist without proof. >>> >>> As people like to point out, Copyright resides with the Copyright owner. For a third party to 'claim' the right to distribute text they are not the Copyright owner of, explicit license had to have been given (a legally binding agreement). What this means for mirrors is this: >>> >>> Anyone can run an FTP service. >>> Anyone can call the directories anything they want in said FTP service. >>> What people place in their FTP servers is where the controversy starts. >>> >>> Others, (not me) have already pointed out that Crosswire doesn't (and can't) control modules once they leave Crosswire's repo. This means Crosswire, as the non-owner, has nothing to say about modules elsewhere. Crosswire tries to asserts legal right over some modules however. There are only two ways under copyright law, Crosswire can exercise rights over copyrighted work: >>> >>> 1. Direct Ownership. Para 106 of of US Copyright law says that the Copyright owner has exclusive rights over their wok, so Crosswire would have to prove it were the Copyright Owner; or >>> 2. Transfer and Licensing of rights. The Owner can transfer rights through formal agreement specificaly expressing those rights (and ultimately granted through a written instrument, signed by the grantor). This is a license, or possibly exclusive license. Under US law, exclusive licenses must be recorded in the US Copyright office or exclusive license is not valid (Para 408) >>> >>> If Crosswire has been exclusively license then, it may establish a rule only certain repositories may distribute modules, but the terms of this license (with the Copyright owner) are not secret (and indeed a matter of public record). >>> If Crosswire has not been exclusively licensed however, Crosswire has no legal right to prohibit others from distributing modules it freely distributes in a non-commercial manner (however much it rants and maligns others). >>> >>> That means for there to be a *.crosswire.org 'rule' Crosswire's exclusive license must be registered and public, or it lacks authority to assert rights over text it doesn't own. People should not get upset when this rule is not followed then. >>> >>> (Don't shoot the messenger because you don't like the law) >>> >>> ~A >>> >>> On Thursday, January 10, 2013, David Blue wrote: >>> Based on the*.crosswire.org rule I would say the best option when and if mirrors are needed is to have some sort of round robin dns that picks a mirror from an internal list the way microsoft.com or my Linux distro does download.opensuse.org for it's package repos. Sorry for the top post' >>> >>> Nic Carter wrote: >>> >>> Sent from my phone, hence this email may be short... >>> >>> On 08/01/2013, at 8:51, Andrew Thule wrote: >>> >>> >>> >>> >>> >>> >>> As long as Crosswire has policies in place govererning official mirrors there should no no worries mirrors are out of sync, in which case preferred mirror selection can be left to the user, and indeed mirror checking behaviour configurable. >>> >>> >>> >>> >>> >>> Yup, policy is no mirrors at this point in time. >>> It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. >>> >>> >>> >>> >>> >>> Easy :) >>> >>> Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) >>> >>> >>> sword-devel mailing list: sword-devel at crosswire.org >>> >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Fri Jan 11 18:25:08 2013 From: chrislit at crosswire.org (Chris Little) Date: Fri, 11 Jan 2013 17:25:08 -0800 Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> Message-ID: <50F0BB74.8020500@crosswire.org> On 1/11/2013 4:08 PM, Andrew Thule wrote: > Nic, no I didn't miss the point. > > You are claiming this privelge is exclusive. If so, the terms of this > agreement must be both registered and public. Anyone can claim anything > they want about what they are able to do, and what others are not able > to do, but these claims are only true if the terms of the law is met. We aren't claiming any exclusive privilege to distribution (except for modules based on materials we create, which are rare). We're stating that we (CrossWire) have permission to distribute certain texts, that permission being granted by their copyright holders. We're pointing out to you that you do not have permission from those copyright holders and are thus in violation of the law and of their copyrights when you redistribute such texts without license. > As long as Crosswire is engaged in the public non-commercial > distribution of modules, and refused to prove its right to do this is > exclusive, it should accept is has no ability to control them > once they've left Crosswire. The idea that we need to prove to you that we have a right to distribute texts is a notion you have invented. It exists only in your own mind. The rest of the world knows no such notion. Similarly, Zondervan does not need to prove to you that they have a right, granted them by Biblica, to print the NIV. That's Zondervan's and Biblica's business and not yours. Their failure to make their agreement public does not grant you automatic right to print NIVs. Please be my guest and demand that Zondervan make its contract with Biblica public. When you get a 'go pound sand' reply, feel free to share it with us. I'm confident we'll all have a good laugh. --Chris From scribe at crosswire.org Fri Jan 11 18:30:45 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sat, 12 Jan 2013 02:30:45 +0100 Subject: [sword-devel] *THREAD CLOSED* (was: CrossWire mirroring) In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> <9E6B87BE-AD95-496B-99BC-400AD3F223BE@mac.com> Message-ID: <50F0BCC5.2020904@crosswire.org> Andrew, Again, we've been over this too many times to continue to flood this list. I will explain it one last time to you, also closing this thread. From ground zero, assume you have zero permission to distribute a work which is copyrighted. CrossWire has asked and received permission from a publisher to distribute a particular copyrighted work. This is not exclusive. Many other people may have been granted permission from the copyright holder. CrossWire's agreement does not give YOU permission to distribute a particular copyrighted work-- it gives CrossWire permission to distribute said work. If you would like permission, simply obtain your own permission from the copyright holders. Though I wouldn't encourage this, as we have already said that we don't see a need for mirrors. Thank you for ceasing this discussion, Troy On 01/12/2013 01:08 AM, Andrew Thule wrote: > Nic, no I didn't miss the point. > > You are claiming this privelge is exclusive. If so, the terms of this > agreement must be both registered and public. Anyone can claim > anything they want about what they are able to do, and what others are > not able to do, but these claims are only true if the terms of the law > is met. > > As long as Crosswire is engaged in the public non-commercial > distribution of modules, and refused to prove its right to do this is > exclusive, it should accept is has no ability to control them > once they've left Crosswire. > > ~A > > On Friday, January 11, 2013, Nic Carter wrote: > > Hi Andrew, > > You completely miss the point! > > CrossWire has the right to distribute certain modules. In order to > satisfy our legal agreement with the copyright holders we can can > only distribute from "CrossWire". We do not own the copyright, we > have to abide by the same rules as anyone else. We are simply in > the awesome position of having been granted permission. > > Also, when I say "we", I am meaning CrossWire. However, even > though I am a volunteer as part of CrossWire, that does not give > me the right to distribute anything. Distribution has to be simply > by CrossWire and the most proper way to satisfy those legal > agreements is to distribute from an official CrossWire domain so > as to strive the hardest to remain above board. :) > > I am now lead to believe that what certain other people have said > here is correct and that you do not understand any of this legal > mumbo jumbo at all, and hence I think you should cease trying to > educate others and instead simply cede to Troy and if you wish to > help with this project, follow his lead, asking him what he wants > of you. > > Thank you. > > Nic... :) > > On 12/01/2013, at 10:40, Andrew Thule > wrote: > >> Ultimately, the issue is about licensing rights on modules, which >> appears to be a very touchy subject around here. I suspect this >> is so because without actual licenses, which are essentially >> legal agreements (I'm not talking about .conf files which are not >> legal agreements), its pretty much impossible to claims >> legal rights and restrictions exist without proof. >> >> As people like to point out, Copyright resides with the Copyright >> owner. For a third party to 'claim' the right to distribute text >> they are not the Copyright owner of, explicit license had to have >> been given (a legally binding agreement). What this means for >> mirrors is this: >> >> Anyone can run an FTP service. >> Anyone can call the directories anything they want in said FTP >> service. >> What people place in their FTP servers is where the controversy >> starts. >> >> Others, (not me) have already pointed out that Crosswire doesn't >> (and can't) control modules once they leave Crosswire's repo. >> This means Crosswire, as the non-owner, has nothing to say about >> modules elsewhere. Crosswire tries to asserts legal right over >> some modules however. There are only two ways under copyright >> law, Crosswire can exercise rights over copyrighted work: >> >> 1. Direct Ownership. Para 106 of of US Copyright law says that >> the Copyright owner has exclusive rights over their wok, so >> Crosswire would have to prove it were the Copyright Owner; or >> 2. Transfer and Licensing of rights. The Owner can transfer >> rights through formal agreement specificaly expressing those >> rights (and ultimately granted through a written instrument, >> signed by the grantor). This is a license, or possibly exclusive >> license. Under US law, exclusive licenses must be recorded in >> the US Copyright office or exclusive license is not valid (Para 408) >> >> If Crosswire has been exclusively license then, it may establish >> a rule only certain repositories may distribute modules, but the >> terms of this license (with the Copyright owner) are not secret >> (and indeed a matter of public record). >> If Crosswire has not been exclusively licensed however, Crosswire >> has no legal right to prohibit others from distributing modules >> it freely distributes in a non-commercial manner (however much it >> rants and maligns others). >> >> That means for there to be a *.crosswire.org >> 'rule' Crosswire's exclusive license must >> be registered and public, or it lacks authority to assert rights >> over text it doesn't own. People should not get upset when this >> rule is not followed then. >> >> (Don't shoot the messenger because you don't like the law) >> >> ~A >> >> On Thursday, January 10, 2013, David Blue wrote: >> >> Based on the*.crosswire.org rule I >> would say the best option when and if mirrors are needed is >> to have some sort of round robin dns that picks a mirror from >> an internal list the way microsoft.com >> or my Linux distro does download.opensuse.org >> for it's package repos. Sorry >> for the top post' >> >> Nic Carter wrote: >> >> Sent from my phone, hence this email may be short... >> >> On 08/01/2013, at 8:51, Andrew Thule wrote: >> >> >> >> >> >> >> As long as Crosswire has policies in place >> govererning official mirrors there should no no >> worries mirrors are out of sync, in which case >> preferred mirror selection can be left to the user, >> and indeed mirror checking behaviour configurable. >> >> >> >> >> >> >> Yup, policy is no mirrors at this point in time. >> It is thought that there _may_ be room in the future for some, but these will be done from a *.crosswire.org domain so as to satisfy copyright requirements. >> >> >> >> >> >> Easy :) >> >> Thanks for your thoughts & I'm glad we can now put this discussion to rest. :) >> >> ------------------------------------------------------------------------ >> >> sword-devel mailing list:sword-devel at crosswire.org >> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From just_mike_y at yahoo.com Sat Jan 12 11:28:10 2013 From: just_mike_y at yahoo.com (Mike Hart) Date: Sat, 12 Jan 2013 10:28:10 -0800 (PST) Subject: [sword-devel] CrossWire mirroring In-Reply-To: References: <3CEDCD72-A883-4686-9BA2-421CB77003D0@crosswire.org> <053588F9-6C23-4ECC-9A85-9485A9C9E99E@mac.com> <5fedf063-667c-4221-9778-8b57d85554fc@email.android.com> Message-ID: <1358015290.39125.YahooMailNeo@web120701.mail.ne1.yahoo.com> Andrew,? The vocabulary is the issue here: There are module repositories already in existence which contain data that is completely compatible with at least some Sword Project programs, but are not mirrors or even part of the the Sword Project.? I know of at least a little overlap between modules hosted on the crosswire.org site and one of these repositories (we'll call it "K"). This "K" repository doesn't claim to be a Crosswire mirror, nor is it listed in any front end (I know of), nor is does it appear on the list of Sword module repositories on the Crosswire website.? The liability for material posted at "K" is clearly separated from Crosswire, and nobody is complaining (publicly anyway.)? Whatever objectionable material, or legal tightrope, or personal decision that caused "K" to be removed from the list is not the point. "K" is a repository that works parallel to but is not part of the Sword Project or Crosswire Bible Society. In all but the Pocketsword program, importing the "K" repository into a sword front end is as easy as adding it to the list manually, and then it works fine.? Your continued use of the word MIRROR implies a (spurious) legal claim that the legal authorization to distribute is pointed at and relies on the source of the mirror and not the host itself.? The University of North Carolina at Chapel Hill (ibiblio.org) maintains 'mirrors' of many linux distributions. I'm sure they claim to be legally innocent when presented with notification of infringement. And under present law, they are innocent? as long as they remove the content from further distribution.? I've seen content go missing from their site before, so I'm pretty sure they've experienced the phrase 'cease and desist' in their many years online. As long as a "mirror" complies in a timely manner to cease and desist notifications, any lawsuits or other legal actions for infringement pass upstream to the various distributions being mirrored: Red Had, or Ubuntu, etc.? Recently, filesharing schemes have exploited this legal hand-off? by trying to claim to be "mirrors" of non-entities. That is, Bittorrents frequently point to IP's that don't exist or worse to innocent uninvolved parties as the original source for questionable material.? Legally each "mirror" isn't liable until they get a piece of paper, but with no 'source', the copyright owners are left filing a missing person report on the IP and proceeding to collect damages from "John Doe."? This loophole is bad enough that in many areas, local/state laws have been changed so there is very little protection for 'unaware copyright infringement,' but the precedent remains in many areas. The national SOPA/PIPA legislation considered last year was all about making "mirrors" fully liable for infringement, regardless of content knowledge. Using a Sword module within the license you received it under is certainly OK, and encouraged as you will read on the crosswire.org site.? However, If you setup a repository and claim in some way to be acting for or under the authorization of Crosswire or sword project, you could legally entangle the Crosswire Bible Society.? Doing a "mirror" (wget -m) on crosswire.org and publishing the resulting mirror without authorization would be fraudulent, and could cause legal consequences for yourself as well as Crosswire, since a clear rule of order within the Crosswire Bible Society seems somewhat chaotic, and proving authorized vs maverick activity might be tricky for the society, especially for a group with no budget facing a well funded legal team. While I'm very much a proponent of getting God's Word onto as many screens as possible, I'm also very aware of devious forces that can and will exploit? legal grey areas to cover or put out this Light.?? Bottom Line: Make all the personal use that your area allows.? Commercially re-release any module that you find allows for it.? Set up a password enabled site and only allow your "friends" to access it.? All these things are great, as long as you separate your activity legally from Crosswire. I haven't read any real argument in the recent chain against being involved in the Great Commision this way.? I think this desire is the core binding force that all of us who are on this list share. However, please don't "Mirror" and hide behind a legal loophole to give away the ESV next to some 'questionable' module that could (in the minds of someone at Crossways) cause harm to the image of the ESV, causing a Cease and Desist letter to crosswire and yourself. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathon.blake at gmail.com Sun Jan 13 11:20:18 2013 From: jonathon.blake at gmail.com (jonathon) Date: Sun, 13 Jan 2013 18:20:18 +0000 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> Message-ID: <50F2FAE2.3010000@gmail.com> On 07/01/13 18:26, Chris Burrell wrote: > Coming back to my original point. > > Is there appetite for such support in the sword modules? I'd suggest that the conf file should contain the breakdown that Peter suggested. (There are a couple of edge cases where a further clarification of rights might be needed, but they can dealt with later.) There are third party programs that utilize .sword content and data, but do not utilize any code or APIs developed by The Sword Project, CrossWire Bible Society, or any front ends, affiliates, etc. Actually, I'd go further, and suggest that the conf file should contain the entire set of Dublin Core Meta Data Elements. jonathon From jhphx at cox.net Sun Jan 13 12:42:56 2013 From: jhphx at cox.net (jhphx) Date: Sun, 13 Jan 2013 12:42:56 -0700 Subject: [sword-devel] Finding out copyright programatically In-Reply-To: <50F2FAE2.3010000@gmail.com> References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> <50F2FAE2.3010000@gmail.com> Message-ID: <50F30E40.8070203@cox.net> On 1/13/2013 11:20 AM, Jonathon wrote: > Actually, I'd go further, and suggest that the conf file should > contain the entire set of Dublin Core Meta Data Elements. jonathon Thanks, I found: http://dublincore.org/documents/dcmi-terms/ interesting and worth looking at. Jerry From dfhmch at googlemail.com Sun Jan 13 12:47:20 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 13 Jan 2013 11:47:20 -0800 (PST) Subject: [sword-devel] Finding out copyright programatically In-Reply-To: <50F2FAE2.3010000@gmail.com> References: <5FA30AC2-8965-4DB0-B74C-4EE811B44654@crosswire.org> <50F2FAE2.3010000@gmail.com> Message-ID: <1358106440765-4651672.post@n4.nabble.com> The idea of making more use in .conf files of http://en.wikipedia.org/wiki/Dublin_Core is commendable, yet for some modules, it might not be so easy to attain. Even so, it would be a useful exercise to see how our existing conf elements map to the Simple *DCMES* of 15 elements. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Finding-out-copyright-programatically-tp4651589p4651672.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sun Jan 13 13:01:47 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 13 Jan 2013 12:01:47 -0800 (PST) Subject: [sword-devel] Trends in mobile platforms Message-ID: <1358107307823-4651673.post@n4.nabble.com> Two recent announcements about mobile platforms caught my attention. These were timed to make the headlines during the CES 2013 in Las Vegas. 1. The advent of *Ubuntu Phone* (formerly Ubuntu Mobile) as an alternative to Android OS. 2. The prospect of *Firefox OS* based mobile & tablet devices based on HTML5. With these in mind, it should prompt thoughts by front-end developers as to the opportunities with these platforms for developing new SWORD or JSword based Bible study applications, or possibly adapting one or more of our existing ones. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673.html Sent from the SWORD Dev mailing list archive at Nabble.com. From kleagkou at gmail.com Mon Jan 14 05:24:32 2013 From: kleagkou at gmail.com (Klearchos-Angelos Gkountras) Date: Mon, 14 Jan 2013 14:24:32 +0200 Subject: [sword-devel] Greek l10n on launhcpad Message-ID: <50F3F900.6090902@gmail.com> I want to contribute on Greek ( my native language) into xiphos and I can't do that , I don't want to download the .po file and but via launchpad My LP account is https://launchpad.net/~jemadux How to contribute ? Thanks -- Klearchos-Angelos Gkountras From dmitrij.ledkov at ubuntu.com Mon Jan 14 05:54:19 2013 From: dmitrij.ledkov at ubuntu.com (Dmitrijs Ledkovs) Date: Mon, 14 Jan 2013 12:54:19 +0000 Subject: [sword-devel] Greek l10n on launhcpad In-Reply-To: <50F3F900.6090902@gmail.com> References: <50F3F900.6090902@gmail.com> Message-ID: On 14 January 2013 12:24, Klearchos-Angelos Gkountras wrote: > I want to contribute on Greek ( my native language) into xiphos and I > can't do that , I don't want to download the .po file and but via launchpad > > My LP account is https://launchpad.net/~jemadux > At one point in time the xiphos translations import/export did work in launchpad. But currently it is failing. Therefore unfortunately it's not currently possible to translate xiphos via launchpad. > How to contribute ? Well, you can try using launchpad staging instance and figure out why the translations import is failing. Regards, Dmitrijs. From refdoc at gmx.net Mon Jan 14 12:14:34 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Mon, 14 Jan 2013 19:14:34 +0000 Subject: [sword-devel] =?utf-8?q?Greek_l10n_on_launhcpad?= Message-ID: Download the po file Sent from my HTC ----- Reply message ----- From: "Klearchos-Angelos Gkountras" To: Subject: [sword-devel] Greek l10n on launhcpad Date: Mon, Jan 14, 2013 12:24 I want to contribute on Greek ( my native language) into xiphos and I can't do that , I don't want to download the .po file and but via launchpad My LP account is https://launchpad.net/~jemadux How to contribute ? Thanks -- Klearchos-Angelos Gkountras _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmedic at gmail.com Mon Jan 14 13:38:47 2013 From: webmedic at gmail.com (webmedic) Date: Mon, 14 Jan 2013 12:38:47 -0800 Subject: [sword-devel] Module creation Message-ID: Hello all I know it's been a long time since I posted anything. The last I was looking at module creation I read a bunch of documentation on osis gbf and vpl. I was rather confused by it all. I have since created quite a few modules for the word as I understand SQL and rtf markup is pretty simple. How easy or hard would it be to convert these to osis or gbf? I don't think I have seen a simple relation type chart or something that says this HTML tag equals this osis tag or this gbf tag. Also in python is there anything for writing sword modules. Thanks Brook Humphrey -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrislit at crosswire.org Mon Jan 14 19:32:02 2013 From: chrislit at crosswire.org (Chris Little) Date: Mon, 14 Jan 2013 18:32:02 -0800 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: , , Message-ID: <50F4BFA2.1090408@crosswire.org> Hi Pola, This looks like a misconfiguration error. Most likely your module .conf either specifies that the module is ThML or the ThML can be (mostly) correctly rendered because it isn't being translated at all and the HTML parts will render almost correctly. Your OSIS looks fine. Please share your .conf and we can tell you where the problem is. --Chris On 1/11/2013 12:02 PM, Pola Edward wrote: > Thanks for the reply, > Attached the images using your markup, no effect in 3 programs > You can see screenshots here > http://depositfiles.com/files/36011rgm3 > > I'm thinking in making the commentaries in intermediate markup format, > so Data entry group can start ASAP, and I'll convert it later to any format > > Note: Xiphos, displayed the ThML markup inside OSIS XML correctly in > previous trials, but other Apps didn't display it the same and just > ignored it > > Pola > > ------------------------------------------------------------------------ > Date: Thu, 10 Jan 2013 00:27:40 -0500 > From: thulester at gmail.com > To: sword-devel at crosswire.org > Subject: Re: [sword-devel] Complete Osis Commentary Example > > If I have a recommendation it is to download the KJV.zip and use the > OSIS examples in their as templates ... > ~A > > On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com > > wrote: > > Could anyone help ?! > > ------------------------------------------------------------------------ > From: 5001 at hotmail.com > To: sword-devel at crosswire.org > Date: Mon, 7 Jan 2013 22:02:48 +0200 > Subject: [sword-devel] Complete Osis Commentary Example > > Hi, > Sorry for sending this to the wrong list, but this list is more > active than osis-users list , My previous post in osis-users list > didn't got attention and i got just 2 replies and no one replied > after my last reply . > > The problem still exists and I've made many many trials, trying to > get it to work > the wiki doesn't contain a complete osis commentary example like > bibles section > > the following is a complete osis structure i tried, it appears in > xiphos and BPBible, but no effect for titles, bold and underline > tags, all texts appear the same in the output . > in programs like Bible Time, I see xml structure instead of normal texts > > Please send me a Complete Osis Commentary Example, so I can follow it > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > osisRefWork="defaultReferenceScheme" xml:lang="en"> >
> > ????? ????? ????? ????? ???? > Bible.FrTadros > Bible.KJV > > > Bible.KJV > >
>
>
> >
type="section"> > This is a > title, and supposed to be bold and underlined >

> > blah blah blah > blah blah blah > Please see James > 1:19 >

>
>
>
>
>
>
> > _______________________________________________ sword-devel mailing > list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions > to unsubscribe/change your settings at above page > > > _______________________________________________ sword-devel mailing > list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From chrislit at crosswire.org Mon Jan 14 19:41:53 2013 From: chrislit at crosswire.org (Chris Little) Date: Mon, 14 Jan 2013 18:41:53 -0800 Subject: [sword-devel] Module creation In-Reply-To: References: Message-ID: <50F4C1F1.8020305@crosswire.org> On 1/14/2013 12:38 PM, webmedic wrote: > Hello all > > I know it's been a long time since I posted anything. The last I was > looking at module creation I read a bunch of documentation on osis gbf > and vpl. I was rather confused by it all. GBF is definitely not supported. Use OSIS. > I have since created quite a few modules for the word as I understand > SQL and rtf markup is pretty simple. > > How easy or hard would it be to convert these to osis or gbf? I don't > think I have seen a simple relation type chart or something that says > this HTML tag equals this osis tag or this gbf tag. RTF and HTML are presentational markup languages. OSIS and TEI are primarily semantic markup languages, though they allow presentational markup to some degree. So producing good OSIS isn't as simple as identifying that RTF {\i1 ...} is HTML ... is OSIS .... Better OSIS will come from determining what you mean by italics and encoding that rather than the italic-ness of the text. So, for example, do italics mark foreign text, emphasis, or titles? Using for presentational markup is, of course, possible, albeit discouraged. > Also in python is there anything for writing sword modules. There should be. Others can comment on the Python bindings. I know that they exist, but haven't tried to use them. --Chris From dfhmch at googlemail.com Tue Jan 15 02:21:35 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 15 Jan 2013 01:21:35 -0800 (PST) Subject: [sword-devel] Greek l10n on launhcpad In-Reply-To: <50F3F900.6090902@gmail.com> References: <50F3F900.6090902@gmail.com> Message-ID: <1358241695333-4651680.post@n4.nabble.com> *And Bible* requires a Greek UI too. Please visit https://code.google.com/p/and-bible/wiki/UserInterfaceTranslation If you need further help, please contact the developer. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Greek-l10n-on-launhcpad-tp4651674p4651680.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Tue Jan 15 04:40:07 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 15 Jan 2013 03:40:07 -0800 (PST) Subject: [sword-devel] Greek l10n on launchpad In-Reply-To: <50F3F900.6090902@gmail.com> References: <50F3F900.6090902@gmail.com> Message-ID: <1358250007255-4651681.post@n4.nabble.com> See also http://crosswire.org/wiki/Choosing_a_SWORD_program#Localization I've just added a row for *???????? (Greek)* in anticipation of the kind offer to translate the Xiphos UI. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Greek-l10n-on-launhcpad-tp4651674p4651681.html Sent from the SWORD Dev mailing list archive at Nabble.com. From refdoc at gmx.net Tue Jan 15 04:52:40 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Tue, 15 Jan 2013 12:52:40 +0100 Subject: [sword-devel] Greek l10n on launhcpad In-Reply-To: <20130114191435.4808gmx1@mp010.gmx.net> References: <20130114191435.4808gmx1@mp010.gmx.net> Message-ID: <20130115115240.162290@gmx.net> >> From: "Klearchos-Angelos Gkountras" >> >> I want to contribute on Greek ( my native language) into xiphos and I >> can't do that , I don't want to download the .po file and but via >> launchpad >> >> My LP account is https://launchpad.net/~jemadux >> >> How to contribute ? > Von: "refdoc at gmx.net" > Download the po file > To clarify, All development happens at Sourceforge. Downloading a po file and using a po file editor is the recommended way forward. At some stage there was an attempt to link it with Launchpad. I think this has come to nothing and I am unaware of anyone having the time or inclination to fix this. Peter From dfhmch at googlemail.com Tue Jan 15 07:01:04 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 15 Jan 2013 06:01:04 -0800 (PST) Subject: [sword-devel] CrossWire Wycliffe modules Message-ID: <1358258464080-4651683.post@n4.nabble.com> It looks as though many of the Central American & Caribbean translations in our CrossWire Wycliffe repository are now available online at Bible Search hosted by the American Bible Society. As the source text for all these modules was provided to CrossWire many years ago, it's quite conceivable that the Bible Search text is more up to date than what we continue to host as modules. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/CrossWire-Wycliffe-modules-tp4651683.html Sent from the SWORD Dev mailing list archive at Nabble.com. From jonmmorgan at gmail.com Tue Jan 15 07:27:08 2013 From: jonmmorgan at gmail.com (Jonathan Morgan) Date: Wed, 16 Jan 2013 01:27:08 +1100 Subject: [sword-devel] Module creation In-Reply-To: <50F4C1F1.8020305@crosswire.org> References: <50F4C1F1.8020305@crosswire.org> Message-ID: Hi, On Tue, Jan 15, 2013 at 1:41 PM, Chris Little wrote: > On 1/14/2013 12:38 PM, webmedic wrote: > >> Hello all >> >> I know it's been a long time since I posted anything. The last I was >> looking at module creation I read a bunch of documentation on osis gbf >> and vpl. I was rather confused by it all. >> > > GBF is definitely not supported. Use OSIS. > > > I have since created quite a few modules for the word as I understand >> SQL and rtf markup is pretty simple. >> >> How easy or hard would it be to convert these to osis or gbf? I don't >> think I have seen a simple relation type chart or something that says >> this HTML tag equals this osis tag or this gbf tag. >> > > RTF and HTML are presentational markup languages. OSIS and TEI are > primarily semantic markup languages, though they allow presentational > markup to some degree. > > So producing good OSIS isn't as simple as identifying that RTF {\i1 ...} > is HTML ... is OSIS .... Better OSIS will > come from determining what you mean by italics and encoding that rather > than the italic-ness of the text. So, for example, do italics mark foreign > text, emphasis, or titles? Using for presentational markup is, of > course, possible, albeit discouraged. > > > Also in python is there anything for writing sword modules. >> > > There should be. Others can comment on the Python bindings. I know that > they exist, but haven't tried to use them. > It is certainly possible to create modules from the Python bindings. BPBible has a wrapper around the functionality which may or may not be a good source of ideas. You can see it at http://code.google.com/p/bpbible/source/browse/trunk/backend/create_module.py. It can both create a module and create its conf file. To write it from scratch, the core calls there would be something like: # Create the SWModule instance. module = SWRawVerse.createModule(path) # Set a value for a key (repeat for all keys you want to set). module.setKey(SWVerseKey("Genesis 1:1")) module.setEntry("Contents of Genesis 1:1") You would then need to set up a conf file, point it to the right directory and so forth. There's a lot more boilerplate in the file I linked to (some of which I don't understand what it does) but the basics should be just "create a module of the write type, and then set values for each key in turn". Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan-husmann at t-online.de Tue Jan 15 09:35:30 2013 From: stefan-husmann at t-online.de (Stefan Husmann) Date: Tue, 15 Jan 2013 17:35:30 +0100 Subject: [sword-devel] Fwd: automake issue under Arch Linux In-Reply-To: <50F2A4AC.3060309@t-online.de> References: <50F2A4AC.3060309@t-online.de> Message-ID: <50F58552.5000002@t-online.de> Betreff: automake issue under Arch Linux Datum: Sun, 13 Jan 2013 13:12:28 +0100 Von: Stefan Husmann An: sword-devel at crosswire.org Hello, this is my first post here, and if it has been brought up already -- I only searched in January and december's mail archives --, I apologize. I am building the sword library from the svn sources and have had problems with aclocal coming with automake 1.13.1. The simple patch at http://paste.pound-python.org/show/29082/ solves this. Please consider it. Best Regards Stefan Husmann From greg.hellings at gmail.com Tue Jan 15 09:44:11 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Tue, 15 Jan 2013 10:44:11 -0600 Subject: [sword-devel] Fwd: automake issue under Arch Linux In-Reply-To: <50F58552.5000002@t-online.de> References: <50F2A4AC.3060309@t-online.de> <50F58552.5000002@t-online.de> Message-ID: Stefan, Does this patch affect the ability of SWORD to compile with the help of older versions of automake, or does it break the older stuff? --Greg On Tue, Jan 15, 2013 at 10:35 AM, Stefan Husmann wrote: > > Betreff: automake issue under Arch Linux > Datum: Sun, 13 Jan 2013 13:12:28 +0100 > Von: Stefan Husmann > An: sword-devel at crosswire.org > > Hello, > > this is my first post here, and if it has been brought up already > -- I only searched in January and december's mail archives --, I apologize. > > I am building the sword library from the svn sources and have had problems > with aclocal coming with automake 1.13.1. > > The simple patch at http://paste.pound-python.org/**show/29082/solves this. > > Please consider it. > > Best Regards Stefan Husmann > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan-husmann at t-online.de Tue Jan 15 10:06:49 2013 From: stefan-husmann at t-online.de (Stefan Husmann) Date: Tue, 15 Jan 2013 18:06:49 +0100 Subject: [sword-devel] Fwd: automake issue under Arch Linux In-Reply-To: References: <50F2A4AC.3060309@t-online.de> <50F58552.5000002@t-online.de> Message-ID: <50F58CA9.3060006@t-online.de> Am 15.01.2013 17:44, schrieb Greg Hellings: > Stefan, > > Does this patch affect the ability of SWORD to compile with the help of > older versions of automake, or does it break the older stuff? > > --Greg > > > On Tue, Jan 15, 2013 at 10:35 AM, Stefan Husmann > wrote: > >> >> Betreff: automake issue under Arch Linux >> Datum: Sun, 13 Jan 2013 13:12:28 +0100 >> Von: Stefan Husmann >> An: sword-devel at crosswire.org >> >> Hello, >> >> this is my first post here, and if it has been brought up already >> -- I only searched in January and december's mail archives --, I apologize. >> >> I am building the sword library from the svn sources and have had problems >> with aclocal coming with automake 1.13.1. >> >> The simple patch at http://paste.pound-python.org/**show/29082/solves this. >> >> Please consider it. >> >> Best Regards Stefan Husmann >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > Greg, according to http://forum.world.st/PATCH-build-don-t-use-obsolescent-AM-PROG-CC-STDC-and-AM-CONFIG-HEADER-td4630038.html the variable AM_CONFIG_HEADER is deprcated since 2002. According to http://www.mail-archive.com/automake at gnu.org/msg18202.html INCLUDES is obsolete since 2003, but in this case only a warning, not a failure, is given by automake 1.13.1. I did not test it, though. Best Regards Stefan From greg.hellings at gmail.com Tue Jan 15 10:15:56 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Tue, 15 Jan 2013 11:15:56 -0600 Subject: [sword-devel] Fwd: automake issue under Arch Linux In-Reply-To: <50F58CA9.3060006@t-online.de> References: <50F2A4AC.3060309@t-online.de> <50F58552.5000002@t-online.de> <50F58CA9.3060006@t-online.de> Message-ID: On Tue, Jan 15, 2013 at 11:06 AM, Stefan Husmann wrote: > Am 15.01.2013 17:44, schrieb Greg Hellings: > >> Stefan, >> >> Does this patch affect the ability of SWORD to compile with the help of >> older versions of automake, or does it break the older stuff? >> >> --Greg >> >> >> On Tue, Jan 15, 2013 at 10:35 AM, Stefan Husmann < >> stefan-husmann at t-online.de >> >>> wrote: >>> >> >> >>> Betreff: automake issue under Arch Linux >>> Datum: Sun, 13 Jan 2013 13:12:28 +0100 >>> Von: Stefan Husmann >>> An: sword-devel at crosswire.org >>> >>> Hello, >>> >>> this is my first post here, and if it has been brought up already >>> -- I only searched in January and december's mail archives --, I >>> apologize. >>> >>> I am building the sword library from the svn sources and have had >>> problems >>> with aclocal coming with automake 1.13.1. >>> >>> The simple patch at http://paste.pound-python.org/****show/29082/ >>> >>> >**solves this. >>> >>> >>> Please consider it. >>> >>> Best Regards Stefan Husmann >>> >>> >>> >>> ______________________________****_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/****mailman/listinfo/sword-devel >>> >>> > >>> >>> Instructions to unsubscribe/change your settings at above page >>> >>> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> Greg, > > according to http://forum.world.st/PATCH-**build-don-t-use-obsolescent-** > AM-PROG-CC-STDC-and-AM-CONFIG-**HEADER-td4630038.htmlthe variable AM_CONFIG_HEADER is deprcated since 2002. > > According to http://www.mail-archive.com/**automake at gnu.org/msg18202.htmlINCLUDES is obsolete since 2003, but in this case only a warning, not a > failure, is given by automake 1.13.1. > I imagine a decade worth of deprecation is probably sufficient to put it out of the requirements of SWORD's targetted support. I believe we usually compare againt any LTS versions of Ubuntu, current Debian and RHEL as our benchmarks for "old enough". AFAIK all of those fall within the past decade with at least one release! --Greg > > I did not test it, though. > > Best Regards Stefan > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kahunapule at mpj.cx Tue Jan 15 10:20:18 2013 From: kahunapule at mpj.cx (Kahunapule Michael Johnson) Date: Tue, 15 Jan 2013 07:20:18 -1000 Subject: [sword-devel] CrossWire Wycliffe modules In-Reply-To: <1358258464080-4651683.post@n4.nabble.com> References: <1358258464080-4651683.post@n4.nabble.com> Message-ID: <50F58FD2.8060207@mpj.cx> An HTML attachment was scrubbed... URL: From kahunapule at mpj.cx Tue Jan 15 10:29:12 2013 From: kahunapule at mpj.cx (Kahunapule Michael Johnson) Date: Tue, 15 Jan 2013 07:29:12 -1000 Subject: [sword-devel] ASV proofreading updates in progress Message-ID: <50F591E8.5030302@mpj.cx> An HTML attachment was scrubbed... URL: From kleagkou at gmail.com Wed Jan 16 12:42:06 2013 From: kleagkou at gmail.com (Klearchos-Angelos Gkountras) Date: Wed, 16 Jan 2013 21:42:06 +0200 Subject: [sword-devel] Greek l10n on launhcpad In-Reply-To: <20130115115240.162290@gmx.net> References: <20130114191435.4808gmx1@mp010.gmx.net> <20130115115240.162290@gmx.net> Message-ID: <50F7028E.9090808@gmail.com> Thanks for your help, I want to contribute by translating the xiphos project ???? 15/01/2013 01:52 ??, ?/? Peter von Kaehne ??????: >>> From: "Klearchos-Angelos Gkountras" >>> >>> I want to contribute on Greek ( my native language) into xiphos and I >>> can't do that , I don't want to download the .po file and but via >>> launchpad >>> >>> My LP account is https://launchpad.net/~jemadux >>> >>> How to contribute ? > >> Von: "refdoc at gmx.net" >> Download the po file >> > > To clarify, > > All development happens at Sourceforge. Downloading a po file and using a po file editor is the recommended way forward. At some stage there was an attempt to link it with Launchpad. I think this has come to nothing and I am unaware of anyone having the time or inclination to fix this. > > Peter > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -- Klearchos-Angelos Gkountras From 5001 at hotmail.com Wed Jan 16 15:39:41 2013 From: 5001 at hotmail.com (Pola Edward) Date: Thu, 17 Jan 2013 00:39:41 +0200 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: <50F4BFA2.1090408@crosswire.org> References: , , , , , , <50F4BFA2.1090408@crosswire.org> Message-ID: Sorry for my late response , these are the contents of my config file [frtadros] DataPath=./modules/comments/rawcom/frtadros/ ModDrv=RawCom Version=0.1 History_0.1=Just Initial Release for testing Encoding=UTF-8 Direction=RtoL Lang=ar Description=????? ????? ????? ????? ???? DistributionLicense=Public Domain TextSource=Original Book Regards, Pola > Date: Mon, 14 Jan 2013 18:32:02 -0800 > From: chrislit at crosswire.org > To: sword-devel at crosswire.org > Subject: Re: [sword-devel] Complete Osis Commentary Example > > Hi Pola, > > This looks like a misconfiguration error. Most likely your module .conf > either specifies that the module is ThML or the ThML can be (mostly) > correctly rendered because it isn't being translated at all and the HTML > parts will render almost correctly. > > Your OSIS looks fine. > > Please share your .conf and we can tell you where the problem is. > > --Chris > > > On 1/11/2013 12:02 PM, Pola Edward wrote: > > Thanks for the reply, > > Attached the images using your markup, no effect in 3 programs > > You can see screenshots here > > http://depositfiles.com/files/36011rgm3 > > > > I'm thinking in making the commentaries in intermediate markup format, > > so Data entry group can start ASAP, and I'll convert it later to any format > > > > Note: Xiphos, displayed the ThML markup inside OSIS XML correctly in > > previous trials, but other Apps didn't display it the same and just > > ignored it > > > > Pola > > > > ------------------------------------------------------------------------ > > Date: Thu, 10 Jan 2013 00:27:40 -0500 > > From: thulester at gmail.com > > To: sword-devel at crosswire.org > > Subject: Re: [sword-devel] Complete Osis Commentary Example > > > > If I have a recommendation it is to download the KJV.zip and use the > > OSIS examples in their as templates ... > > ~A > > > > On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com > > > wrote: > > > > Could anyone help ?! > > > > ------------------------------------------------------------------------ > > From: 5001 at hotmail.com > > To: sword-devel at crosswire.org > > Date: Mon, 7 Jan 2013 22:02:48 +0200 > > Subject: [sword-devel] Complete Osis Commentary Example > > > > Hi, > > Sorry for sending this to the wrong list, but this list is more > > active than osis-users list , My previous post in osis-users list > > didn't got attention and i got just 2 replies and no one replied > > after my last reply . > > > > The problem still exists and I've made many many trials, trying to > > get it to work > > the wiki doesn't contain a complete osis commentary example like > > bibles section > > > > the following is a complete osis structure i tried, it appears in > > xiphos and BPBible, but no effect for titles, bold and underline > > tags, all texts appear the same in the output . > > in programs like Bible Time, I see xml structure instead of normal texts > > > > Please send me a Complete Osis Commentary Example, so I can follow it > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > > > > osisRefWork="defaultReferenceScheme" xml:lang="en"> > >
> > > > ????? ????? ????? ????? ???? > > Bible.FrTadros > > Bible.KJV > > > > > > Bible.KJV > > > >
> >
> >
> > > >
> type="section"> > > This is a > > title, and supposed to be bold and underlined > >

> > > > blah blah blah > > blah blah blah > > Please see James > > 1:19 > >

> >
> >
> >
> >
> >
> >
> > > > _______________________________________________ sword-devel mailing > > list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions > > to unsubscribe/change your settings at above page > > > > > > _______________________________________________ sword-devel mailing > > list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > > unsubscribe/change your settings at above page > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Wed Jan 16 15:43:04 2013 From: dmsmith at crosswire.org (DM Smith) Date: Wed, 16 Jan 2013 17:43:04 -0500 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: , , , , , , <50F4BFA2.1090408@crosswire.org> Message-ID: You are missing: SourceType=OSIS It is defaulting to Plaintext. On Jan 16, 2013, at 5:39 PM, Pola Edward <5001 at hotmail.com> wrote: > Sorry for my late response , > these are the contents of my config file > > [frtadros] > DataPath=./modules/comments/rawcom/frtadros/ > ModDrv=RawCom > Version=0.1 > History_0.1=Just Initial Release for testing > Encoding=UTF-8 > Direction=RtoL > Lang=ar > Description=????? ????? ????? ????? ???? > DistributionLicense=Public Domain > TextSource=Original Book > > Regards, > Pola > > > Date: Mon, 14 Jan 2013 18:32:02 -0800 > > From: chrislit at crosswire.org > > To: sword-devel at crosswire.org > > Subject: Re: [sword-devel] Complete Osis Commentary Example > > > > Hi Pola, > > > > This looks like a misconfiguration error. Most likely your module .conf > > either specifies that the module is ThML or the ThML can be (mostly) > > correctly rendered because it isn't being translated at all and the HTML > > parts will render almost correctly. > > > > Your OSIS looks fine. > > > > Please share your .conf and we can tell you where the problem is. > > > > --Chris > > > > > > On 1/11/2013 12:02 PM, Pola Edward wrote: > > > Thanks for the reply, > > > Attached the images using your markup, no effect in 3 programs > > > You can see screenshots here > > > http://depositfiles.com/files/36011rgm3 > > > > > > I'm thinking in making the commentaries in intermediate markup format, > > > so Data entry group can start ASAP, and I'll convert it later to any format > > > > > > Note: Xiphos, displayed the ThML markup inside OSIS XML correctly in > > > previous trials, but other Apps didn't display it the same and just > > > ignored it > > > > > > Pola > > > > > > ------------------------------------------------------------------------ > > > Date: Thu, 10 Jan 2013 00:27:40 -0500 > > > From: thulester at gmail.com > > > To: sword-devel at crosswire.org > > > Subject: Re: [sword-devel] Complete Osis Commentary Example > > > > > > If I have a recommendation it is to download the KJV.zip and use the > > > OSIS examples in their as templates ... > > > ~A > > > > > > On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com > > > > wrote: > > > > > > Could anyone help ?! > > > > > > ------------------------------------------------------------------------ > > > From: 5001 at hotmail.com > > > To: sword-devel at crosswire.org > > > Date: Mon, 7 Jan 2013 22:02:48 +0200 > > > Subject: [sword-devel] Complete Osis Commentary Example > > > > > > Hi, > > > Sorry for sending this to the wrong list, but this list is more > > > active than osis-users list , My previous post in osis-users list > > > didn't got attention and i got just 2 replies and no one replied > > > after my last reply . > > > > > > The problem still exists and I've made many many trials, trying to > > > get it to work > > > the wiki doesn't contain a complete osis commentary example like > > > bibles section > > > > > > the following is a complete osis structure i tried, it appears in > > > xiphos and BPBible, but no effect for titles, bold and underline > > > tags, all texts appear the same in the output . > > > in programs like Bible Time, I see xml structure instead of normal texts > > > > > > Please send me a Complete Osis Commentary Example, so I can follow it > > > > > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > > > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > > > > > > > osisRefWork="defaultReferenceScheme" xml:lang="en"> > > >
> > > > > > ????? ????? ????? ????? ???? > > > Bible.FrTadros > > > Bible.KJV > > > > > > > > > Bible.KJV > > > > > >
> > >
> > >
> > > > > >
> > type="section"> > > > This is a > > > title, and supposed to be bold and underlined > > >

> > > > > > blah blah blah > > > blah blah blah > > > Please see James > > > 1:19 > > >

> > >
> > >
> > >
> > >
> > >
> > >
> > > > > > _______________________________________________ sword-devel mailing > > > list: sword-devel at crosswire.org > > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions > > > to unsubscribe/change your settings at above page > > > > > > > > > _______________________________________________ sword-devel mailing > > > list: sword-devel at crosswire.org > > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > > > unsubscribe/change your settings at above page > > > > > > > > > _______________________________________________ > > > sword-devel mailing list: sword-devel at crosswire.org > > > http://www.crosswire.org/mailman/listinfo/sword-devel > > > Instructions to unsubscribe/change your settings at above page > > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5001 at hotmail.com Thu Jan 17 01:13:19 2013 From: 5001 at hotmail.com (Pola Edward) Date: Thu, 17 Jan 2013 10:13:19 +0200 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: , ,,, , , , , , , <50F4BFA2.1090408@crosswire.org>, , Message-ID: Thanks a lot, it worked :) every program displayed it differently, but at least it's more readable as i want . That's why i asked for a complete Osis Commentary example, single line ruined my plan for more than 2 weeks :) I'll try to make account on the wiki, and write more info. there Thanks to everyone Helped me . I'll modify the OSIS Commentary editor to produce the new markup . Will keep you updated :) Thanks again Pola From: dmsmith at crosswire.org Date: Wed, 16 Jan 2013 17:43:04 -0500 To: sword-devel at crosswire.org Subject: Re: [sword-devel] Complete Osis Commentary Example You are missing:SourceType=OSISIt is defaulting to Plaintext. On Jan 16, 2013, at 5:39 PM, Pola Edward <5001 at hotmail.com> wrote:Sorry for my late response , these are the contents of my config file [frtadros] DataPath=./modules/comments/rawcom/frtadros/ ModDrv=RawCom Version=0.1 History_0.1=Just Initial Release for testing Encoding=UTF-8 Direction=RtoL Lang=ar Description=????? ????? ????? ????? ???? DistributionLicense=Public Domain TextSource=Original Book Regards, Pola > Date: Mon, 14 Jan 2013 18:32:02 -0800 > From: chrislit at crosswire.org > To: sword-devel at crosswire.org > Subject: Re: [sword-devel] Complete Osis Commentary Example > > Hi Pola, > > This looks like a misconfiguration error. Most likely your module .conf > either specifies that the module is ThML or the ThML can be (mostly) > correctly rendered because it isn't being translated at all and the HTML > parts will render almost correctly. > > Your OSIS looks fine. > > Please share your .conf and we can tell you where the problem is. > > --Chris > > > On 1/11/2013 12:02 PM, Pola Edward wrote: > > Thanks for the reply, > > Attached the images using your markup, no effect in 3 programs > > You can see screenshots here > > http://depositfiles.com/files/36011rgm3 > > > > I'm thinking in making the commentaries in intermediate markup format, > > so Data entry group can start ASAP, and I'll convert it later to any format > > > > Note: Xiphos, displayed the ThML markup inside OSIS XML correctly in > > previous trials, but other Apps didn't display it the same and just > > ignored it > > > > Pola > > > > ------------------------------------------------------------------------ > > Date: Thu, 10 Jan 2013 00:27:40 -0500 > > From: thulester at gmail.com > > To: sword-devel at crosswire.org > > Subject: Re: [sword-devel] Complete Osis Commentary Example > > > > If I have a recommendation it is to download the KJV.zip and use the > > OSIS examples in their as templates ... > > ~A > > > > On Wednesday, January 9, 2013, Pola Edward <5001 at hotmail.com > > > wrote: > > > > Could anyone help ?! > > > > ------------------------------------------------------------------------ > > From: 5001 at hotmail.com > > To: sword-devel at crosswire.org > > Date: Mon, 7 Jan 2013 22:02:48 +0200 > > Subject: [sword-devel] Complete Osis Commentary Example > > > > Hi, > > Sorry for sending this to the wrong list, but this list is more > > active than osis-users list , My previous post in osis-users list > > didn't got attention and i got just 2 replies and no one replied > > after my last reply . > > > > The problem still exists and I've made many many trials, trying to > > get it to work > > the wiki doesn't contain a complete osis commentary example like > > bibles section > > > > the following is a complete osis structure i tried, it appears in > > xiphos and BPBible, but no effect for titles, bold and underline > > tags, all texts appear the same in the output . > > in programs like Bible Time, I see xml structure instead of normal texts > > > > Please send me a Complete Osis Commentary Example, so I can follow it > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace > > http://www.bibletechnologies.net/osisCore.2.1.1.xsd"> > > > > > osisRefWork="defaultReferenceScheme" xml:lang="en"> > >
> > > > ????? ????? ????? ????? ???? > > Bible.FrTadros > > Bible.KJV > > > > > > Bible.KJV > > > >
> >
> >
> > > >
> type="section"> > > This is a > > title, and supposed to be bold and underlined > >

> > > > blah blah blah > > blah blah blah > > Please see James > > 1:19 > >

> >
> >
> >
> >
> >
> >
> > > > _______________________________________________ sword-devel mailing > > list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions > > to unsubscribe/change your settings at above page > > > > > > _______________________________________________ sword-devel mailing > > list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > > unsubscribe/change your settings at above page > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Thu Jan 17 01:46:07 2013 From: dfhmch at googlemail.com (David Haslam) Date: Thu, 17 Jan 2013 00:46:07 -0800 (PST) Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: References: <50F4BFA2.1090408@crosswire.org> Message-ID: <1358412366519-4651695.post@n4.nabble.com> Always useful to learn from users' difficulties, so I've just added this short section: http://crosswire.org/wiki/OSIS_Commentaries#Config_file David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Complete-Osis-Commentary-Example-tp4651633p4651695.html Sent from the SWORD Dev mailing list archive at Nabble.com. From 5001 at hotmail.com Thu Jan 17 01:49:54 2013 From: 5001 at hotmail.com (Pola Edward) Date: Thu, 17 Jan 2013 10:49:54 +0200 Subject: [sword-devel] Complete Osis Commentary Example In-Reply-To: <1358412366519-4651695.post@n4.nabble.com> References: , , , , <50F4BFA2.1090408@crosswire.org>, , , <1358412366519-4651695.post@n4.nabble.com> Message-ID: Like :) Thanks David > Date: Thu, 17 Jan 2013 00:46:07 -0800 > From: dfhmch at googlemail.com > To: sword-devel at crosswire.org > Subject: Re: [sword-devel] Complete Osis Commentary Example > > Always useful to learn from users' difficulties, so I've just added this > short section: > > http://crosswire.org/wiki/OSIS_Commentaries#Config_file > > David > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/Complete-Osis-Commentary-Example-tp4651633p4651695.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From rieske.will at gmail.com Thu Jan 17 07:17:52 2013 From: rieske.will at gmail.com (Will Rieske) Date: Thu, 17 Jan 2013 09:17:52 -0500 Subject: [sword-devel] Jumping in Message-ID: Hello all. I'm Will, and I'd like some info on how to start helping out here. I'm a second-semester C++ student, and a Christian trying to advance the Kingdom and my portfolio simultaneously. Can I help at my level? Thanks, -Will -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Thu Jan 17 08:22:55 2013 From: dfhmch at googlemail.com (David Haslam) Date: Thu, 17 Jan 2013 07:22:55 -0800 (PST) Subject: [sword-devel] Jumping in In-Reply-To: References: Message-ID: <1358436175760-4651698.post@n4.nabble.com> Welcome Will, Please visit our developers' wiki. http://crosswire.org/wiki/ Browse the pages, use the categories, visit the notable front-end sites, etc. See if you find something that matches your interest and skills. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Jumping-in-tp4651697p4651698.html Sent from the SWORD Dev mailing list archive at Nabble.com. From scribe at crosswire.org Sat Jan 19 09:13:26 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sat, 19 Jan 2013 17:13:26 +0100 Subject: [sword-devel] Method Name Normalization Message-ID: <50FAC626.3000304@crosswire.org> In anticipation of a new release, I have a large checkin I'm about to commit which will break everything for everyone compiling with -Werror. We've been normalizing method names toward a clean API interface at 2.0. SWORD started 20+ years ago when there was not standard naming conventions. In fact, originally we tried to keep variable names less than 8 characters, as, at the time, some compilers stopped disambiguating after this. Besides these, there are a number of conventions we used back then for which standards have now become the norm: camelCase conventions, standard set/getProperty naming, and the like. We've been slowly moving toward these changes and have been deprecating old names for a few years now. What I'm about to introduces standard names for all methods within the SWKey and SWModule classes and deprecates the non standard names. A few not obvious changes: Headings() has been renamed to setIntros(bool) and bool isIntros() Headings() -- used to turn on chapter, book, testament, and module introductions, has frequently been a point of confusion with the global option "Headings" -- used to turn on and off section headings in the text. This new property name will hopefully remove that confusion. Error() has become popError(), as the functionality has always been to return and clear any error code for the object. The bindings are probably in a state of disarray now. I've updated the omniorb bindings. I'd appreciated any help with other stuff. I hope this doesn't cause too much of a headache for everyone. I hope these naming standards raise coherence to the look of our API for newcomers. Hope you are all at the start of a blessed new year, Troy From scribe at crosswire.org Sat Jan 19 09:28:40 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sat, 19 Jan 2013 17:28:40 +0100 Subject: [sword-devel] XHTML Filterset Message-ID: <50FAC9B8.9030803@crosswire.org> I've done my part and changed one more tag. transChange has been upgraded from: to: .transChangeSupplied { font-style: italic; } More changes welcome. Nic, you mentioned doing similar work on your own copies of our filters. Any experience you'd like to share? Bibletime, same. I know you guys have had stuff styled for quite some time. Would ultimately like to get this filter set to something we all can share and improve. Troy From greg.hellings at gmail.com Sat Jan 19 09:52:56 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sat, 19 Jan 2013 10:52:56 -0600 Subject: [sword-devel] XHTML Filterset In-Reply-To: <50FAC9B8.9030803@crosswire.org> References: <50FAC9B8.9030803@crosswire.org> Message-ID: On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts wrote: > I've done my part and changed one more tag. transChange has been upgraded > from: > > > to: > > .transChangeSupplied { > font-style: italic; > } > > > > More changes welcome. > > Nic, you mentioned doing similar work on your own copies of our filters. > Any experience you'd like to share? > > Bibletime, same. I know you guys have had stuff styled for quite some > time. > BT outputs the following (found on lines 383ff of src/backend/filters/osistohtml.cpp): ...... where **type** is the value of the type attribute of transChange. If no type attribute is specified, the value of the changeType attribute is used. If the type or changeType attribute of transChange is equal to "added" then the outer span gets a title="Added text" and if it is equal to "tenseChange" it gets a title="Verb tense changed" added to it. Only some of our styles have CSS associated with the .transchange, but those which do have font-style=italic. Looking at the particular C++ code, I see a very straightforward simplification we could do for it, so I'll probably simplify that logic down. --Greg > > Would ultimately like to get this filter set to something we all can share > and improve. > > Troy > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Sat Jan 19 10:14:27 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sat, 19 Jan 2013 11:14:27 -0600 Subject: [sword-devel] SFTP Support In-Reply-To: References: <50D7DC71.1040002@crosswire.org> <50E10268.4040505@crosswire.org> <50E9D0AB.7010801@crosswire.org> Message-ID: On Tue, Jan 8, 2013 at 2:39 PM, Greg Hellings wrote: > Thanks! I updated CMake as we talked about. > > The current SVN HEAD of Xiphos now has support for adding SFTP sources > through its module manager. Shout-out to Karl (or whoever wrote that > dialog) for making the code there very straightforward. Just adding a > source with type "SFTP" in Xiphos' module manager will create the > necessary entry in InstallMgr.conf and any SFTP sources that SWORD > reports will act normally. > I've also added the ability to create/modify HTTP, HTTPS and SFTP transports to BibleTime, although it still lacks the ability to specify a username or password. Support can be found in the branch sword-svn-compat from the BibleTime repositories. However, it probably will not compile if your build of SWORD has Troy's check in from earlier this morning. --Greg > > Note that SWORD will silently and harmlessly ignore any > InstallMgr.conf entries that are SFTPSource entries if it was compiled > without SFTP support. > > --Greg > > On Sun, Jan 6, 2013 at 1:29 PM, Troy A. Griffitts > wrote: > > Applied. Thanks Greg, for the original contribution and for taking the > time > > to work through the details. > > > > > > On 12/31/2012 03:53 PM, Greg Hellings wrote: > > > > Here is the updated patch adding CURLSFTPAVAILABLE support to CMake as > > well as to the library code. It defaults to assuming no SFTP support > > if either the curl-config executable cannot be found or if it returns > > a value other than "1" from the quick detection process we have > > settled on. > > > > Users of Windows builds through either VisualStudio or Borland will > > need to figure out if curl-config is available on their systems and, > > if not, come up with another way to detect and support SFTP for > > clients using those builds. On Linux it is a Bash script, so it might > > be adaptable to Manfred's XCode system in some way also. > > > > For those in the JSword world, I am sure there are SFTP Java clients > > available which could be leveraged if they wanted to add support for > > the same functionality to JSword applications. > > > > --Greg > > > > On Sun, Dec 30, 2012 at 9:11 PM, Troy A. Griffitts > > > wrote: > > > > OK Greg, > > > > I've hacked detection of CURL SFTP into the autotools build (hopefully-- > it > > works for me). > > > > I've added a new compile time define with -DCURLSFTPAVAILABLE to go along > > with the existing -DCURLAVAILABLE > > > > If you'd like to update the sftp patch to conditionally compile support > in > > based on this define, that would be cool. I'll do it myself soon if you > > don't have time. > > > > Troy > > > > > > > > On 12/28/2012 11:42 AM, Greg Hellings wrote: > > > > Further digging with help from our friends has revealed this nugget: > > > > $ curl-config --protocols > > > > produces a newline-delimited list of protocols that the particular > > build of libcurl supports. curl-config is a shell script which can be > > run on the build system and should satisfy both the requirements of > > native builds and cross-compiling support. We could use this to set a > > compiler macro indicating support (or not) for SFTP in the target > > libcurl library. > > > > If someone wants to tackle that in the autotools world, I can add > > detection to CMake as well. A simple command such as > > $ curl-config --protocols | grep SFTP | wc -l > > 1 > > > > in Fedora will result in a value of 1 or greater if SFTP is supported > > while it should produce 0 if SFTP support is left out. An Ubuntu > > system produce this output: > > $ curl-config --protocols | grep SFTP | wc -l > > 0 > > > > And it even works for cross-compiling: > > $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols | > > grep SFTP | wc -l > > 1 > > > > > > This appears to be our best way forward if we want to enable > > compile-time enabling or disabling of this option. > > > > --Greg > > > > On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings > > wrote: > > > > Troy, > > > > On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts > > wrote: > > > > Dear Greg, > > > > Looking to apply this SFTP patch, could you give me some background as > > to > > why the check to ignore across all transports for '.' and '..'? > > > > Our downloading method runs recursively from the given directory until > > it runs out of directory depth. FTP servers don't usually seem to > > return . and .. as valid paths, and the HTTP(S) transport attempts to > > parse the returned HTML page to avoid the link to the parent > > directory. But whatever options are passed by cURL to the SFTP > > transport resulted in it returning . and .. as paths within the > > current directory. Because '.' came first in the list, the installmgr > > was running through an infinite loop whenever it tried to pull data > > from the server. > > > > I added it at the level of all transports because we don't want to > > either loop infinitely on '.' or accidentally pull a whole server > > recursively by following '..' to the root of the server. It might be a > > server config option that permits it, but I wanted to avoid the > > possibility of the InlstallMgr class getting choked up on it. > > > > --Greg > > > > Thanks, > > > > Troy > > > > > > > > > > On 12/03/2012 04:06 PM, Greg Hellings wrote: > > > > The attached patch will introduce support for SFTPSource transports in > > the SWORD engine, allowing a user to access remote repositories over > > SFTP (which is enabled by default when a user enables SSH). > > > > --Greg > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sat Jan 19 10:43:59 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 19 Jan 2013 09:43:59 -0800 (PST) Subject: [sword-devel] XHTML Filterset In-Reply-To: <50FAC9B8.9030803@crosswire.org> References: <50FAC9B8.9030803@crosswire.org> Message-ID: <1358617439009-4651703.post@n4.nabble.com> *Observation:* Not all writing systems support italics! e.g. How do or should we display transChange items for Chinese? c.f. An established method in printed texts is to use dotted underline. Is our XHTML filterset capable of addressing such requirements? If not, how might this be achieved? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/XHTML-Filterset-tp4651700p4651703.html Sent from the SWORD Dev mailing list archive at Nabble.com. From refdoc at gmx.net Sat Jan 19 11:28:56 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sat, 19 Jan 2013 18:28:56 +0000 Subject: [sword-devel] XHTML Filterset In-Reply-To: References: <50FAC9B8.9030803@crosswire.org> Message-ID: <1358620136.2815.4.camel@peter-ThinkPad-Twist> On Sat, 2013-01-19 at 10:52 -0600, Greg Hellings wrote: > On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts > > > > > BT outputs the following (found on lines 383ff of > src/backend/filters/osistohtml.cpp): > ...... > I would second the BT change as slightly better than the one you proposed, Troy. In essence the more info reaches in stylable fashion the frontends the more can be done with it, eventually. Even if right now no one is using this. Similarly notes - we use in essence two types only - "normal" notes and xrefs, but OSIS allows for a lot more. I could see modules coming to a place where we want to be able to switch on and off only certain types of notes. Peter From refdoc at gmx.net Sat Jan 19 11:31:59 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sat, 19 Jan 2013 18:31:59 +0000 Subject: [sword-devel] Method Name Normalization In-Reply-To: <50FAC626.3000304@crosswire.org> References: <50FAC626.3000304@crosswire.org> Message-ID: <1358620319.2815.7.camel@peter-ThinkPad-Twist> On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: > > Headings() has been renamed to setIntros(bool) and bool isIntros() > Headings() -- used to turn on chapter, book, testament, and module > introductions, has frequently been a point of confusion with the global > option "Headings" -- used to turn on and off section headings in the > text. This new property name will hopefully remove that confusion. Does this mean that headings and intros are now formally separated? Right now both are turned on jointly, while a more natural way would be to turn on headings and turn on intros separately of each other - maybe making latter dependent on former, but former should be possible without sudden appearance of huge intro paragraphes. Peter From greg.hellings at gmail.com Sat Jan 19 11:41:55 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sat, 19 Jan 2013 12:41:55 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: <1358620319.2815.7.camel@peter-ThinkPad-Twist> References: <50FAC626.3000304@crosswire.org> <1358620319.2815.7.camel@peter-ThinkPad-Twist> Message-ID: On Sat, Jan 19, 2013 at 12:31 PM, Peter von Kaehne wrote: > On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: > > > > Headings() has been renamed to setIntros(bool) and bool isIntros() > > Headings() -- used to turn on chapter, book, testament, and module > > introductions, has frequently been a point of confusion with the global > > option "Headings" -- used to turn on and off section headings in the > > text. This new property name will hopefully remove that confusion. > > Does this mean that headings and intros are now formally separated? > Right now both are turned on jointly, while a more natural way would be > to turn on headings and turn on intros separately of each other - maybe > making latter dependent on former, but former should be possible without > sudden appearance of huge intro paragraphes. > I can only speak about Xiphos and BibleTime, as those are the only two I have used: Xiphos you still have to request the 0'th chapter in order to see the introduction, and with BibleTime, the window is pre-scrolled past the Headings and the user needs to scroll back to read them if they want to. I was thrown off the first time I was looking for module header information in BT because the module window was scrolled beyond it. --Greg > > Peter > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Sat Jan 19 12:30:55 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sat, 19 Jan 2013 20:30:55 +0100 Subject: [sword-devel] Method Name Normalization In-Reply-To: <1358620319.2815.7.camel@peter-ThinkPad-Twist> References: <50FAC626.3000304@crosswire.org> <1358620319.2815.7.camel@peter-ThinkPad-Twist> Message-ID: <155fad9e-a18e-44d6-bbd3-b2535e663357@email.android.com> Peter von Kaehne wrote: >On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: >> >> Headings() has been renamed to setIntros(bool) and bool isIntros() >> Headings() -- used to turn on chapter, book, testament, and module >> introductions, has frequently been a point of confusion with the >global >> option "Headings" -- used to turn on and off section headings in the >> text. This new property name will hopefully remove that confusion. > >Does this mean that headings and intros are now formally separated? They always have been. They have never had anything to do with each other. >Right now both are turned on jointly, Maybe a tool or frontend you've used does this, bit the engine has no correlation between the two. Troy while a more natural way would be >to turn on headings and turn on intros separately of each other - maybe >making latter dependent on former, but former should be possible >without >sudden appearance of huge intro paragraphes. > >Peter > > >_______________________________________________ >sword-devel mailing list: sword-devel at crosswire.org >http://www.crosswire.org/mailman/listinfo/sword-devel >Instructions to unsubscribe/change your settings at above page -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. From dmsmith at crosswire.org Sat Jan 19 14:12:56 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sat, 19 Jan 2013 16:12:56 -0500 Subject: [sword-devel] Vertical whitespace Message-ID: <88779976-CE1C-4F94-B6B2-B685C3C25752@crosswire.org> I've noticed that OSIS modules sometimes render with a lot of vertical whitespace (blank lines). I'd like for this to be sorted as part of the next release. I don't think it'd be too hard. I've been in the osishtmlhref filter to see if I could figure it out, but it is beyond me. So this is a suggestion for others. Using the HTML notion of block and inline elements, I think we can classify OSIS elements as block or inline. Off the top of my head,
, ,

, , , , , <table> and <row> are the block elements. The key feature of a block element is that block elements that follow each other stack one on top of each other. Some block elements allow nesting, such as <div>. In HTML, an empty <div> occupies no vertical space. A nested div does not cause additional vertical space. In HTML, a <p> has semantics as to whether it is preceded or followed by whitespace. A <p> at the beginning of a document is not preceded by a blank line. Nor is a </p> at the end of a document. This is also true after a heading element. I think that the SWORD renderers always cause a <div> to occupy vertical whitespace. The other issue with <div> is that we now have a "pre-verse" div, which is a great way of marking off what stands before a verse, but this <div> really shouldn't have any <div> semantic. It probably would have been better if we used <milestone> instead. I seem to remember that there is a "swollow" flag for whitespace (I think it might be for horizontal whitespace.) I think something like this could be used for vertical whitespace. The other part to this is when a chapter is shown verse-per-line. If because of rendering the pre-verse content the verse already starts on a new line, I don't think more vertical whitespace should be produced. Together in His Service, DM From refdoc at gmx.net Sat Jan 19 14:16:55 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Sat, 19 Jan 2013 21:16:55 +0000 Subject: [sword-devel] Method Name Normalization In-Reply-To: <155fad9e-a18e-44d6-bbd3-b2535e663357@email.android.com> References: <50FAC626.3000304@crosswire.org> <1358620319.2815.7.camel@peter-ThinkPad-Twist> <155fad9e-a18e-44d6-bbd3-b2535e663357@email.android.com> Message-ID: <1358630215.2815.9.camel@peter-ThinkPad-Twist> On Sat, 2013-01-19 at 20:30 +0100, Troy A. Griffitts wrote: > > Peter von Kaehne <refdoc at gmx.net> wrote: > >Does this mean that headings and intros are now formally separated? > > They always have been. They have never had anything to do with each other. On Xiphos these are the same. Turn on headings and intro stuff appears. Turn it off and it goes. Or is there a module bug? Look e.g. at Sorani Kurdish. But many others are the same. Peter From dmsmith at crosswire.org Sat Jan 19 15:04:19 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sat, 19 Jan 2013 17:04:19 -0500 Subject: [sword-devel] Pre-verse div and headings Message-ID: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> This might be related to the other thread of name normalization that is discussing intros and headings. Prior to the pre-verse div, everything that was pre-verse was a title, aka heading. The purpose of the pre-verse div was to allow any kind of markup between verses. The net result is that all markup in the input (once we get past the OSIS header) is kept (though possibly transformed). The only exception to this is the <verse> element. It is not retained. Osis2mod heuristically splits the material between verses by appending some of it to the prior and keeping the rest of it with the next. Simplistically, after </verse> (or it's equivalent) it looks for an opening tag and having seen that quits appending and starting the pre-verse for the next. With the more recent modules, there is a lot of structural information between verses. This may or may not contain headings. It may or may not contain introductory material. The structural material needs to be rendered whether or not headings are being rendered. I don't think this is the case. I hear that when headings is on, there is too much vertical whitespace, but when it is off sanity returns. I'd like to see this fixed. The kinds of structural material that appears between verses is typically section divs and paragraphs. But it may also contain poetry containers (i.e. <lg> and <l>) Regarding introductory material, we have support through Chapter 0 and Verse 0 of book and chapter introductions. But I don't think we have support for section introductory material (I haven't seen it in a module either, so the question is anticipatory). In the past, I've viewed the "headings" toggle as a toggle for non-canonical material. But the discussion on the other thread has me wondering whether intros (non-canonical) information is handled by it. But if we have a section that starts in the middle of a chapter and that section has a title and a paragraph or two of introduction, how is that to be handled? Together in His Service, DM From jonmmorgan at gmail.com Sun Jan 20 02:43:50 2013 From: jonmmorgan at gmail.com (Jonathan Morgan) Date: Sun, 20 Jan 2013 20:43:50 +1100 Subject: [sword-devel] XHTML Filterset In-Reply-To: <CAHxvOV+s=VR0ZdmPKtPD0RzA_e07=VVF2Mj20B0MJXb2hQnftw@mail.gmail.com> References: <50FAC9B8.9030803@crosswire.org> <CAHxvOV+s=VR0ZdmPKtPD0RzA_e07=VVF2Mj20B0MJXb2hQnftw@mail.gmail.com> Message-ID: <CAOOKcO4rWWU_gh6N1XMDvU4eBNO6vRVD+qsKkqsPurfmTn9+qg@mail.gmail.com> Hi Greg, On Sun, Jan 20, 2013 at 3:52 AM, Greg Hellings <greg.hellings at gmail.com>wrote: > > > > On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts <scribe at crosswire.org>wrote: > >> I've done my part and changed one more tag. transChange has been >> upgraded from: >> <i></i> >> >> to: >> >> .transChangeSupplied { >> font-style: italic; >> } >> >> <span class="transChangeSupplied"></**span> >> >> More changes welcome. >> >> Nic, you mentioned doing similar work on your own copies of our filters. >> Any experience you'd like to share? >> >> Bibletime, same. I know you guys have had stuff styled for quite some >> time. >> > > BT outputs the following (found on lines 383ff of > src/backend/filters/osistohtml.cpp): > <span class="transchange"><span class="**type**"> ...... </span></span> > > where **type** is the value of the type attribute of transChange. If no > type attribute is specified, the value of the changeType attribute is used. > If the type or changeType attribute of transChange is equal to "added" then > the outer span gets a title="Added text" and if it is equal to > "tenseChange" it gets a title="Verb tense changed" added to it. > Would you really want a title to be output for this? It seems very specific markup, quite different from the "class based" markup, and also raises the questions "How do we change the text displayed for a transChange? Or translate it? Or show it in some other way than a tooltip?" Jon > > Only some of our styles have CSS associated with the .transchange, but > those which do have font-style=italic. > > Looking at the particular C++ code, I see a very straightforward > simplification we could do for it, so I'll probably simplify that logic > down. > > --Greg > > >> >> Would ultimately like to get this filter set to something we all can >> share and improve. >> >> Troy >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/b387d35c/attachment.html> From greg.hellings at gmail.com Sun Jan 20 08:25:47 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 09:25:47 -0600 Subject: [sword-devel] XHTML Filterset In-Reply-To: <CAOOKcO4rWWU_gh6N1XMDvU4eBNO6vRVD+qsKkqsPurfmTn9+qg@mail.gmail.com> References: <50FAC9B8.9030803@crosswire.org> <CAHxvOV+s=VR0ZdmPKtPD0RzA_e07=VVF2Mj20B0MJXb2hQnftw@mail.gmail.com> <CAOOKcO4rWWU_gh6N1XMDvU4eBNO6vRVD+qsKkqsPurfmTn9+qg@mail.gmail.com> Message-ID: <CAHxvOV+PX6z+AosNVDPfK4hE8d86+w=NDQKDzg5Vw9OR-BjzMw@mail.gmail.com> On Sun, Jan 20, 2013 at 3:43 AM, Jonathan Morgan <jonmmorgan at gmail.com>wrote: > Hi Greg, > > On Sun, Jan 20, 2013 at 3:52 AM, Greg Hellings <greg.hellings at gmail.com>wrote: > >> >> >> >> On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts <scribe at crosswire.org >> > wrote: >> >>> I've done my part and changed one more tag. transChange has been >>> upgraded from: >>> <i></i> >>> >>> to: >>> >>> .transChangeSupplied { >>> font-style: italic; >>> } >>> >>> <span class="transChangeSupplied"></**span> >>> >>> More changes welcome. >>> >>> Nic, you mentioned doing similar work on your own copies of our filters. >>> Any experience you'd like to share? >>> >>> Bibletime, same. I know you guys have had stuff styled for quite some >>> time. >>> >> >> BT outputs the following (found on lines 383ff of >> src/backend/filters/osistohtml.cpp): >> <span class="transchange"><span class="**type**"> ...... </span></span> >> >> where **type** is the value of the type attribute of transChange. If no >> type attribute is specified, the value of the changeType attribute is used. >> If the type or changeType attribute of transChange is equal to "added" then >> the outer span gets a title="Added text" and if it is equal to >> "tenseChange" it gets a title="Verb tense changed" added to it. >> > > Would you really want a title to be output for this? It seems very > specific markup, quite different from the "class based" markup, and also > raises the questions "How do we change the text displayed for a transChange? > I'm thinking we may have gotten our wires crossed in that line. The title is not instead of the class but in addition to. So a <transChange type="tenseChange"> is replaced with <span class="transchange" title="Verb tense changed"><span class="tenseChange">**textual content of original**</span></span> So the CSS still works as intended. Granted, you can set CSS selectors on arbitrary attributes with XPath-inspired syntax if you have a new enough rendering engine, which both BibleTime and Xiphos have at this time. Based on the code, I'm guessing this handling was originally limited to only added and tenseChange and later people just got a little lazy with it and didn't add in those titles. > Or translate it? > It's translated the same way every other UI string in BibleTime is translated. buf.append("<span class=\"transchange\" title=\""); buf.append(QObject::tr("Verb tense changed").toUtf8().constData()); buf.append("\"><span class=\"tenseChange\">"); > Or show it in some other way than a tooltip?" > At least in the QtWebKit bindings, you can listen in on mouseover/hover events and pull out the text of the elements to display it however you want. Also, to be clear, I wasn't suggesting that this BT code is /the way to go/, I was just answering Troy's question about how do those frontends which customize their HTML renderers handle the transChange element by telling him what the BT code does for the sake of comparison and discussion. --Greg > > Jon > > >> >> Only some of our styles have CSS associated with the .transchange, but >> those which do have font-style=italic. >> >> Looking at the particular C++ code, I see a very straightforward >> simplification we could do for it, so I'll probably simplify that logic >> down. >> >> --Greg >> >> >>> >>> Would ultimately like to get this filter set to something we all can >>> share and improve. >>> >>> Troy >>> >>> >>> >>> ______________________________**_________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> >>> Instructions to unsubscribe/change your settings at above page >>> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/65858274/attachment-0001.html> From jaak at ristioja.ee Sun Jan 20 10:36:04 2013 From: jaak at ristioja.ee (Jaak Ristioja) Date: Sun, 20 Jan 2013 19:36:04 +0200 Subject: [sword-devel] Patches to fix compiler warnings In-Reply-To: <50E5F400.9020700@ristioja.ee> References: <50D3A00E.8060909@ristioja.ee> <A4286341-3D73-4874-87BE-E74D7DDB7DC2@mac.com> <50E5F400.9020700@ristioja.ee> Message-ID: <50FC2B04.8040805@ristioja.ee> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Is there any progress regarding the patches I sent? A month has passed since I submitted them and there has been no feedback. Blessings Jaak On 03.01.2013 23:11, Jaak Ristioja wrote: > On 02.01.2013 09:22, Nic Carter wrote: >> Thanks for these. > >> Hopefully some kind soul will apply them? > > When I first posted the patches I thought I'll wait until 2013 > before taking any further steps. But it has been a very busy time > for me and possibly also for the Sword developers, so I think I'll > wait a little more until I have more time to work on Sword (maybe > some time next week). > >> For those who are interested, some fun articles related to this >> stuff: > >> * >> http://inessential.com/2012/12/31/coders_in_the_hands_of_an_angry_god > >> > > * http://boredzo.org/blog/archives/2009-11-07/warnings >> * (more appropriate to Obj-C) >> http://ashfurrow.com/blog/seven-deadly-sins-of-modern-objective-c > >> > I can't fully agree with the "treat all warnings as errors" > approach, since as far as I know there are some warnings which are > very difficult to work around, e.g. warnings about "#pragma STDC > FENV_ACCESS ON" not being supported by certain compilers or Clang > warnings about struct/class padding. Some warnings can be > annotated with comments (which might also show up in the warnings) > so that developers wouldn't try to fix what can't be fixed in a > straightforward manner. > > In my opinion short variable names are also fine if they are > either simple temporary variables, if their declarations are well > documented or if their semantics are obvious just by looking at > their type. Of course longer and more descriptive names are > recommended, but in case stuff doesn't fit well horizontally I've > usually abbreviated them, especially if their scope is limited. The > biggest issue with short variable names is that they sometimes (and > not very rarely) make code difficult to read and understand. > > > Blessings, Jaak -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQgcBAEBAgAGBQJQ/Cr3AAoJEEqsYmEt1rCOFY5AALgNSBaRQFVufVg9qQtDXBbW prMqRqMolx3Es9mTmCCsDaXzpYeNZagx04aNma7wrKE3LN1FvHyMqMA4+ajHUuEi rBDuZLSkrfn2xWWdaC2uh0qmVQrfvfip07TyuordOQT5HtRKWIPTu8q00YxvpHUX QN/YfafmVfr4815j+t+tWmVt3pFiHc3N1iFYBDy85NFbQvKCJVwZEKyhShU0O8mv lFBHr2GsuiTJDxc2RgGIDVIgPrEk0MOH2IFkmeXVj0/Ms6pzjDHNwM48vAD3K5e3 BzUTGyvlH/HMjWazqCwNxxFoLYwBTJOsySlh9aLBGVdN0WyLyYMadtzmMrkcJ6od uhPA+e801+vvEKkNKcvxjR0+x8cWNjLTEuaSXMX16TELHC5bP28IsRnUj+0I6VAf Sj5ROn3KeyFE2gGkq7K1setMV7yXb8IHGpF6/U+l7+O0rC7peIfMG/RQijFr+4ON I/eOkv+AzUgKhAkJDrfr8KNjD0oLx6F2ojvo7N/otVsVJE8nfe0Dv0cruSWq+AUh JAdEF+Mcm2Z7hSseXDNBYuYiB3TjjI0PcGvCM4blshCvzZ7LsVzaiq5Gt7EMj2Yw yo1Y7yMxQwopGXMvaWC90QmSmQkKZAP4uJmKFHdZuPBeChWJXGJ514pcDYbW6QVL MTold54iogp7Z/nJAnFUDK/y+0fmYFPnsb2BKLbY1BkE7GAq3lUG8Mq/Kwz/lkYN JNZtN0yWyupm4aSkYWBrzGq0Kgz4W/xLMRIqS9BjeUfQ+Dhb+LaMF+yVG1k0zX5s 6Wz7dtWF6tjIjWHUJTphZQJ4kyobmnmu5ymFS7itsgwHEL2NjGjAHQtANqB91Eyi SuQyL77Xs02wm8OmdNFkpj2GJeA9MVVZtyNRuz9TFAzKQrucVDVIeaRmx9NjE/VS oO89MqCiu0MG+OAMIp7p7y2MYZ5dEcsIbGd7wvfghUeJMUcM7dQKtgWE+jE/LKsf zwNaQ1oeyvKK85z3H50rqX5+BsdueRdgaCt8gueqc8kNkzCXMjSfswFwjiAXmcH7 0rVrDMjCpXwDuoMkcVd/I/l7bCusRtiEyCBjbp7LVm4ryOBK5Te+iMR5MMMb3KD/ Lb1D73xMot8ly+X+8N7f9//qn7DwteF3JrjDX2I85kN3wC41Wd9gLblRghAVuMvz VefmNP6CpgnyDPh7RyjNBdc6p0sR1T7LWdMFoHh4LHxNvB3JYqlDIypg3tmcA4qP W4IktBfFe6oWtJ2r+9Xtx2deJjkLJEhfCrw3O792jrH6kIXEnG70dLVFGuDHnB3U lROVFWHWqwZGGwFQR0YYeplwRjXACtf6zeBtrbqigxyHxeXxAHpu/K6eDYrSxyzj b0WHwfzBPl4EOTNLiVYWTkPV+kAw47VTLMR7ME8uJef7vuPdIC4pFYCRCA65/wa1 +f3QGGy8AiMc+1D2Sd8ceIaqUjOv8X4GVZ+s1qx4QH5Pjxw8kUm6mmo/MppztZBc uR1oc2LAH5uzYUMGy1YmFNzqFMeWkfTD2W/1eiEMa17BZ/aiM4vscPsYte8BsO+1 m1wWgi9PjtfLpeKcqdJgjPS2/LlsExdlHDrZIx47A6mWaDcYr7E/iiHzuFpFCJvH SFbESkhxOapXStckxro55++c2fiNk9IBhPvvLRe+kJTbSBnRYo2shIzypGwdgOxa nSI6P4z1kC7LTnDDRMSk1vrhR603POmFzjDJBtrDIIP9p3iindFN5btLIr10OctA TYfHk02/0U0mctzVdJYmt9bNUB6AtXADJsRkCJhjzq4pYOmjf5BbIS6TJ4cSAuQq d028TjM0kRJdXboF7pK9OyYGFUz3y45N8u/A+WwU65SA22t9NNqHKYmh4UH8hZdL 5pQ0XkfsEIiBCyVKxMnRJV6X+padziD8bqkA/rB/7ZOFVEIoSFvncAsQHcTeeWBM 0nR0Ub7pymmOba6STyUbAsz91cXBYPb6PFVIfjxjqVS2U8PJIFR0hlA6f+0mZ54f gu5pQ07PDBJPf8FC6c+HssZR3DCz/7CTgzG/C8Dd9wyoLEjh86WoRIWIlZyhr9U6 XdZ080J0EvZJU0CgaICi3tPvLa69T1TFCEJL7KkQOgRSQ9Fa+QfbSYT0sy3Upu8l KvJGtDaRfKfhV3aAwXrg/Mx8/sPcs0W86g5R3IjeA+GHB4NRDBSZue341MtPM8qq KewJNU0ExlKGFtaSdw2c3jnzprdKvKAnIbLfPwjm8tO3xDtAM6mcPoDrvvF915HC GILzbWNUi7d++gVjmsUQ/MkXMDfp6auHG5i6b1+mokkG+fOoaRS/80Ok87W15HoG 5AqCULWHqeKNVkmc7gDWlMEL3tW2zwim7RWjTE/v7de3ILlpPe1nvxaudBZemPT1 etG+vACio52h3DOanKsme/NORlsVWEb9VWewMxErP7GbCwRh3izUpShGmAZ6oD3h W+KybocZjJiBsDw4nvUorofgV/uW2OIXkvvynMW296m1leo7FymQHXcXC81wIIpw /EID1Wi5Sx+frKhVXd4FSfhfpVURTl0gmt+d0j92ODkIFimI+udloZru02noTymN RJS6Rmo+G0fr6ySuZ1euXNrSozmGTcJrTy5nxnfP66uZkPM/fMOf6Vmm+50NZdVD AgmrAwzvup8OBb6PPhGmcnPMSlHXerghV5RmJdJj3aYO3jyJuyq2/VZGKDm7QNcQ 9u/GdN2pLOIODBg9R9bB =lTc4 -----END PGP SIGNATURE----- From greg.hellings at gmail.com Sun Jan 20 10:44:15 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 11:44:15 -0600 Subject: [sword-devel] Extra warnings Message-ID: <CAHxvOVJvBGwiC3F_8pyoad+Aqarh=mZn8nwwC1rYwGzFvkHp9w@mail.gmail.com> I don't know if you fixed this in this week's super-commit, as I'm just about to try and build BibleTime against that, but InstallMgr::getCipherCode has long been throwing the pair of warnings "unused parameter `modName'" and "unused parameter `config'" because it is defined with the method body "{ return false; }". Is there a way to handle this differently - either implement it as a pure virtual or work it around to not throw these errors? --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/3896b205/attachment.html> From greg.hellings at gmail.com Sun Jan 20 11:00:18 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 12:00:18 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: <50FAC626.3000304@crosswire.org> References: <50FAC626.3000304@crosswire.org> Message-ID: <CAHxvOVLX36noSs7rSsdRxQm3_WhapAoWD82p+W4FPJaZrGPpbA@mail.gmail.com> Building the library (with CMake) now I get many warnings coming from examples/cmdline. Among those I get the following errors: /home/greg/Source/sword/examples/cmdline/threaded_search.cpp:101: undefined reference to `sword::VerseKey::ParseVerseList(char const*, char const*, bool, bool)' collect2: error: ld returned 1 exit status /home/greg/Source/sword/examples/cmdline/verserangeparse.cpp:48: undefined reference to `sword::VerseKey::ParseVerseList(char const*, char const*, bool, bool)' collect2: error: ld returned 1 exit status /home/greg/Source/sword/examples/cmdline/search.cpp:102: undefined reference to `sword::VerseKey::ParseVerseList(char const*, char const*, bool, bool)' collect2: error: ld returned 1 exit status It looks like this has become parseVerseList now and you just missed those couple of places. --Greg On Sat, Jan 19, 2013 at 10:13 AM, Troy A. Griffitts <scribe at crosswire.org>wrote: > In anticipation of a new release, I have a large checkin I'm about to > commit which will break everything for everyone compiling with -Werror. > > We've been normalizing method names toward a clean API interface at 2.0. > SWORD started 20+ years ago when there was not standard naming > conventions. In fact, originally we tried to keep variable names less than > 8 characters, as, at the time, some compilers stopped disambiguating after > this. Besides these, there are a number of conventions we used back then > for which standards have now become the norm: camelCase conventions, > standard set/getProperty naming, and the like. We've been slowly moving > toward these changes and have been deprecating old names for a few years > now. What I'm about to introduces standard names for all methods within > the SWKey and SWModule classes and deprecates the non standard names. > > A few not obvious changes: > > Headings() has been renamed to setIntros(bool) and bool isIntros() > Headings() -- used to turn on chapter, book, testament, and module > introductions, has frequently been a point of confusion with the global > option "Headings" -- used to turn on and off section headings in the text. > This new property name will hopefully remove that confusion. > > Error() has become popError(), as the functionality has always been to > return and clear any error code for the object. > > The bindings are probably in a state of disarray now. I've updated the > omniorb bindings. I'd appreciated any help with other stuff. > > I hope this doesn't cause too much of a headache for everyone. I hope > these naming standards raise coherence to the look of our API for newcomers. > > Hope you are all at the start of a blessed new year, > > Troy > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/8326651a/attachment.html> From greg.hellings at gmail.com Sun Jan 20 11:04:29 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 12:04:29 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: <CAHxvOVLX36noSs7rSsdRxQm3_WhapAoWD82p+W4FPJaZrGPpbA@mail.gmail.com> References: <50FAC626.3000304@crosswire.org> <CAHxvOVLX36noSs7rSsdRxQm3_WhapAoWD82p+W4FPJaZrGPpbA@mail.gmail.com> Message-ID: <CAHxvOV+h5WLXbFY_45JGbq+SU0-KeScRZLhHEMRYazi5H3VxBg@mail.gmail.com> Attached is a patch (I don't think I have commit privileges to that directory? If so, I can commit it directly.). --Greg On Sun, Jan 20, 2013 at 12:00 PM, Greg Hellings <greg.hellings at gmail.com>wrote: > Building the library (with CMake) now I get many warnings coming from > examples/cmdline. Among those I get the following errors: > /home/greg/Source/sword/examples/cmdline/threaded_search.cpp:101: > undefined reference to `sword::VerseKey::ParseVerseList(char const*, char > const*, bool, bool)' > collect2: error: ld returned 1 exit status > /home/greg/Source/sword/examples/cmdline/verserangeparse.cpp:48: undefined > reference to `sword::VerseKey::ParseVerseList(char const*, char const*, > bool, bool)' > collect2: error: ld returned 1 exit status > /home/greg/Source/sword/examples/cmdline/search.cpp:102: undefined > reference to `sword::VerseKey::ParseVerseList(char const*, char const*, > bool, bool)' > collect2: error: ld returned 1 exit status > > It looks like this has become parseVerseList now and you just missed those > couple of places. > > --Greg > > > On Sat, Jan 19, 2013 at 10:13 AM, Troy A. Griffitts <scribe at crosswire.org>wrote: > >> In anticipation of a new release, I have a large checkin I'm about to >> commit which will break everything for everyone compiling with -Werror. >> >> We've been normalizing method names toward a clean API interface at 2.0. >> SWORD started 20+ years ago when there was not standard naming >> conventions. In fact, originally we tried to keep variable names less than >> 8 characters, as, at the time, some compilers stopped disambiguating after >> this. Besides these, there are a number of conventions we used back then >> for which standards have now become the norm: camelCase conventions, >> standard set/getProperty naming, and the like. We've been slowly moving >> toward these changes and have been deprecating old names for a few years >> now. What I'm about to introduces standard names for all methods within >> the SWKey and SWModule classes and deprecates the non standard names. >> >> A few not obvious changes: >> >> Headings() has been renamed to setIntros(bool) and bool isIntros() >> Headings() -- used to turn on chapter, book, testament, and module >> introductions, has frequently been a point of confusion with the global >> option "Headings" -- used to turn on and off section headings in the text. >> This new property name will hopefully remove that confusion. >> >> Error() has become popError(), as the functionality has always been to >> return and clear any error code for the object. >> >> The bindings are probably in a state of disarray now. I've updated the >> omniorb bindings. I'd appreciated any help with other stuff. >> >> I hope this doesn't cause too much of a headache for everyone. I hope >> these naming standards raise coherence to the look of our API for newcomers. >> >> Hope you are all at the start of a blessed new year, >> >> Troy >> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/4150469d/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 04-big-refactor-examples.patch Type: application/octet-stream Size: 1611 bytes Desc: not available URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/4150469d/attachment-0001.obj> From jaak at ristioja.ee Sun Jan 20 11:06:11 2013 From: jaak at ristioja.ee (Jaak Ristioja) Date: Sun, 20 Jan 2013 20:06:11 +0200 Subject: [sword-devel] Patch to speed up iterator incrementation Message-ID: <50FC3213.6080202@ristioja.ee> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! The attached patch corrects all Sword code where iterators were incremented using postfix operator++(int) in contexts where the return value of the expression was not used. Prefix operator++() should be used to avoid the creation of temporary iterators on every increment. Blessings, Jaak -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQgcBAEBAgAGBQJQ/DIIAAoJEEqsYmEt1rCOT6c//2aGj9d2/iww6aEoE/4hg4U8 SIOaUYjm8yPo/hMUUtyU/DTV4qJJL1m832UFDxXOygoMKQGcT2KR0x4wwRrOJJQT JoJo8Y6EqmQ7weGC6ivV6Aj4zdwTkWC+cwi74utcurnPBnyt+RlhikJJz0Ez/sHm VEn1IYsdwjAYPekJD7wqyYu2WNstI7jaIHYQB6IH3+IR/19DQ7Z4nz5AoY+9o6XE 764TGW1QD9pyUgvQJQJDudPj5WnHx16eDf+Vwv2wxY3adjG059pnfJ3Ib6OoqCKE IjFTsjfZoqYOW+tsoJIYaenlEsSiUjnNs0XWehdXZb4RGx3KPFiCXIOcLfXDXxtg xi1Vs4yyTfB9DkpsWjQeSrKlIiF1T+F0grr+tVI5lCHX+7raNM0ZGYP26FeJj9Te ws+9DdGgaW6u5sp3aLzMxtXIPH/LYt7eZXj1zxf4Mp989n3XjZz7nSeEcBZVxytq Vfh0ui5YY4CRedAhiUkChzJ34Lse7EW6ztxMxZTim4C5IAYxSDcFnmYN6At2xTwb CULOqNAATmNC2FrmM67/RHUU6kCnK6EqFfRZVR9ZL4M4nPQsrGrYKccpIf/nWM1W zjEZIrI1mGi77pGu76XR86VNzMYjOGuIk70eSYRRkVUy9LkiPUdOtwnNrOVFPf+V a0mzZOB+ZwYBlbZvhutemzGQ7TX8PNi/umWfjEMTrs9l1v9Xd+RlyakV2mOFwsaN 8jsXAy2CqPdIkMgbgENBGK5otZpnsYir3uLr4tsAPstInQqD+IH+Zd+2kteTDfSz 6oty6fSyleowH0ZhBcL7AgaO4/QIwzJy9OIJl0dr3QVXnuPlErIUb6tc3R9fODEv LTXQiGMnG58GQuZFtchi35uLaMzGD87r/7TQndAWHtgIJ0l4w80CsZfYW1dhvL8y I9yiFcsi9h3pjKTpkcAa5RfZKCZeCRoITFtABgItpMrweMjTVOcgEIZkA5SdNdX6 7ZfaDEGRjmqyzVU26+OUQfq9iwBHQ+RZlz3jHy+JSbs5TqmgAKpv8sWQb5/JEbTQ sYK62DwtOrARVu7HnKB1H7WB/FuTYlljHn0IMjm+ApTVh0LYYD80az264Y4uew0p arWewrK1xNTfICrTXHEjp31CrxrgoPl89HidpbwGMSaMePE06tLr/4q1gh4bAelY w1Oh2MELFIl2p2YsAi8MKi5d/lfy6drRt/itWVECjfK2H2tKWBJk3UU3CXlfNLxH C7Ec2zrncmjLNA8xV0ziK9v3j/4QuarfOyjIpxdiuMCileU9xFZlzTgUWB0JIuFN 0W31R9FypbvXAL8/E+fZlE0zyuo6SgWxHPFqFjaCtb+/xORlCCYQFnBLTsljjWlY SIM7c+N9gZhh7C/4Hzg0zgjEBrppc05ZNQf3j+ZSYtSwyqYDk5mqQQ19xUrgh+B+ Y0Oef0KnD6XG0imco5H5rEOajPXURNc48wvdyODN1Kjzaq1b/ODe/xvB9qFY+/9x u62ytfmJIFY4rWVNyqWj2QCTfUrLTC04xz4DSMOLH81X5I7/kyX8ZHIaU69lgze8 FO2msCmgzmIhnneqtISVKZmfoYXZyDcRYS2q6AtTyVUj4FDz8053ssDSp+hrz4Ep c9+JuvHiHePK1EiNhwLrkFelCbUK0RGVntE1c2y2ey0I/czDxGcCiEwr8SmaUfiF RltPp4bCG0wLemrtl1kLeGaur3KLayoigPLj+7oK4GWIC6SEK4NAjfX6UIFg9DB3 yhCsXMfzK0p5mZ1XdMrozXVFnjL8cAsWJmXdw8Sm+OOPDUmIwIg7CZZKYMcuscZO xkwKcPSrHz4/o30Kvcho6ArWILrVntbfurn78k1j2YNhoiGdjFFl5vUmJzEVWfa2 8L7ijaUpLue40HM3zIY/QS8N6IXykZ3iYQTsDwccwLk2sja/dwYxutaxs7T9fMVu DckO3avg4xZBPOfvj5agmI7rOiLcRmOhcHmMvof4c+SV9B4EMj47RQtzXruGWdIR mAzixcnHoxhhz32yoNiO3KeYVyP/KGGnB/e0l2N1GOnjViT0Y+Re0ilRYml/9Z6B wnvXy1CcMr7tIVcEbGGdh16pziXSBo/kB2GWpprgDar7r1s6Ga/anGP7NL2GoLrF 5ETaBZHqgfJGD0/RgnVy5NZC+E4WwWxFEPS3O1h1NLuvUyjdoUA0XZBoZVIDmvgz bZjrTnIqp01L6PBcnl4+E+E9xAYQVWY1zzgHHVzCdKxw/xPPWmgHlkSwFlHr+4es Y06SR5bK2ezQDykiObFs/P0dIv8K1mgFdU7YPc/IYYqH7PznzR90T616B4jvQuSc Hg/R2ybFQqPPfHScT5XXdH7Ws1a0u4lqSs9jt0zu6xEpT2seDzJW3spkEnNphM6R bycyI0J7yU9pfUHP9XmbbyoQUjIMHuiA0ZBFPx5DTNP7Ij6JiPlMR4oSBxVDjayu vkk+I+HN8VlgcOeELQhAB34Tzs39kZTY6IAAutiavelsFmq+XBVNdHyli25oiARj /Ozbk0FHiWuNDdVs4shTtSVUkKRGuAFyDTymjSNKvmtIwtOLI53ok1JJA/yOu9kg 6Nen2L0mVHSl4JDkSYVuM20k7wKnfT5vZjbikbIaXrNwQFXki3Mz1QQcivQvzEp4 kYge36a96eqN6ECJmk+3iy/+gwfoCr8V65eI6oWW5NUi27ox8P2kQz9RBvNYo0gi ZV3JzAWDpuZWJSSL//4i =feb5 -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: sword-iterators-postfix-to-prefix.diff.bz2 Type: application/x-bzip Size: 3602 bytes Desc: not available URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/5f6a6ea3/attachment.bin> From greg.hellings at gmail.com Sun Jan 20 12:28:21 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 13:28:21 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: <50FAC626.3000304@crosswire.org> References: <50FAC626.3000304@crosswire.org> Message-ID: <CAHxvOVJn801uJ_+XeT2SxAw98mzUwbTL6cKyRvPZkUTPb6z2xw@mail.gmail.com> On Sat, Jan 19, 2013 at 10:13 AM, Troy A. Griffitts <scribe at crosswire.org>wrote: > In anticipation of a new release, I have a large checkin I'm about to > commit which will break everything for everyone compiling with -Werror. > > We've been normalizing method names toward a clean API interface at 2.0. > SWORD started 20+ years ago when there was not standard naming > conventions. In fact, originally we tried to keep variable names less than > 8 characters, as, at the time, some compilers stopped disambiguating after > this. Besides these, there are a number of conventions we used back then > for which standards have now become the norm: camelCase conventions, > standard set/getProperty naming, and the like. We've been slowly moving > toward these changes and have been deprecating old names for a few years > now. What I'm about to introduces standard names for all methods within > the SWKey and SWModule classes and deprecates the non standard names. > > A few not obvious changes: > > Headings() has been renamed to setIntros(bool) and bool isIntros() > Headings() -- used to turn on chapter, book, testament, and module > introductions, has frequently been a point of confusion with the global > option "Headings" -- used to turn on and off section headings in the text. > This new property name will hopefully remove that confusion. > > Error() has become popError(), as the functionality has always been to > return and clear any error code for the object. > > The bindings are probably in a state of disarray now. I've updated the > omniorb bindings. I'd appreciated any help with other stuff. > SWIG bindings now up-to-date. Bindings users, please holler if I removed things overzealously. --Greg > > I hope this doesn't cause too much of a headache for everyone. I hope > these naming standards raise coherence to the look of our API for newcomers. > > Hope you are all at the start of a blessed new year, > > Troy > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/e02c2da5/attachment.html> From scribe at crosswire.org Sun Jan 20 14:02:32 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sun, 20 Jan 2013 22:02:32 +0100 Subject: [sword-devel] Patch to speed up iterator incrementation In-Reply-To: <50FC3213.6080202@ristioja.ee> References: <50FC3213.6080202@ristioja.ee> Message-ID: <50FC5B68.5040503@crosswire.org> Applied. Thanks Jaak! On 01/20/2013 07:06 PM, Jaak Ristioja wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi! > > The attached patch corrects all Sword code where iterators were > incremented using postfix operator++(int) in contexts where the return > value of the expression was not used. Prefix operator++() should be > used to avoid the creation of temporary iterators on every increment. > > Blessings, > Jaak > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iQgcBAEBAgAGBQJQ/DIIAAoJEEqsYmEt1rCOT6c//2aGj9d2/iww6aEoE/4hg4U8 > SIOaUYjm8yPo/hMUUtyU/DTV4qJJL1m832UFDxXOygoMKQGcT2KR0x4wwRrOJJQT > JoJo8Y6EqmQ7weGC6ivV6Aj4zdwTkWC+cwi74utcurnPBnyt+RlhikJJz0Ez/sHm > VEn1IYsdwjAYPekJD7wqyYu2WNstI7jaIHYQB6IH3+IR/19DQ7Z4nz5AoY+9o6XE > 764TGW1QD9pyUgvQJQJDudPj5WnHx16eDf+Vwv2wxY3adjG059pnfJ3Ib6OoqCKE > IjFTsjfZoqYOW+tsoJIYaenlEsSiUjnNs0XWehdXZb4RGx3KPFiCXIOcLfXDXxtg > xi1Vs4yyTfB9DkpsWjQeSrKlIiF1T+F0grr+tVI5lCHX+7raNM0ZGYP26FeJj9Te > ws+9DdGgaW6u5sp3aLzMxtXIPH/LYt7eZXj1zxf4Mp989n3XjZz7nSeEcBZVxytq > Vfh0ui5YY4CRedAhiUkChzJ34Lse7EW6ztxMxZTim4C5IAYxSDcFnmYN6At2xTwb > CULOqNAATmNC2FrmM67/RHUU6kCnK6EqFfRZVR9ZL4M4nPQsrGrYKccpIf/nWM1W > zjEZIrI1mGi77pGu76XR86VNzMYjOGuIk70eSYRRkVUy9LkiPUdOtwnNrOVFPf+V > a0mzZOB+ZwYBlbZvhutemzGQ7TX8PNi/umWfjEMTrs9l1v9Xd+RlyakV2mOFwsaN > 8jsXAy2CqPdIkMgbgENBGK5otZpnsYir3uLr4tsAPstInQqD+IH+Zd+2kteTDfSz > 6oty6fSyleowH0ZhBcL7AgaO4/QIwzJy9OIJl0dr3QVXnuPlErIUb6tc3R9fODEv > LTXQiGMnG58GQuZFtchi35uLaMzGD87r/7TQndAWHtgIJ0l4w80CsZfYW1dhvL8y > I9yiFcsi9h3pjKTpkcAa5RfZKCZeCRoITFtABgItpMrweMjTVOcgEIZkA5SdNdX6 > 7ZfaDEGRjmqyzVU26+OUQfq9iwBHQ+RZlz3jHy+JSbs5TqmgAKpv8sWQb5/JEbTQ > sYK62DwtOrARVu7HnKB1H7WB/FuTYlljHn0IMjm+ApTVh0LYYD80az264Y4uew0p > arWewrK1xNTfICrTXHEjp31CrxrgoPl89HidpbwGMSaMePE06tLr/4q1gh4bAelY > w1Oh2MELFIl2p2YsAi8MKi5d/lfy6drRt/itWVECjfK2H2tKWBJk3UU3CXlfNLxH > C7Ec2zrncmjLNA8xV0ziK9v3j/4QuarfOyjIpxdiuMCileU9xFZlzTgUWB0JIuFN > 0W31R9FypbvXAL8/E+fZlE0zyuo6SgWxHPFqFjaCtb+/xORlCCYQFnBLTsljjWlY > SIM7c+N9gZhh7C/4Hzg0zgjEBrppc05ZNQf3j+ZSYtSwyqYDk5mqQQ19xUrgh+B+ > Y0Oef0KnD6XG0imco5H5rEOajPXURNc48wvdyODN1Kjzaq1b/ODe/xvB9qFY+/9x > u62ytfmJIFY4rWVNyqWj2QCTfUrLTC04xz4DSMOLH81X5I7/kyX8ZHIaU69lgze8 > FO2msCmgzmIhnneqtISVKZmfoYXZyDcRYS2q6AtTyVUj4FDz8053ssDSp+hrz4Ep > c9+JuvHiHePK1EiNhwLrkFelCbUK0RGVntE1c2y2ey0I/czDxGcCiEwr8SmaUfiF > RltPp4bCG0wLemrtl1kLeGaur3KLayoigPLj+7oK4GWIC6SEK4NAjfX6UIFg9DB3 > yhCsXMfzK0p5mZ1XdMrozXVFnjL8cAsWJmXdw8Sm+OOPDUmIwIg7CZZKYMcuscZO > xkwKcPSrHz4/o30Kvcho6ArWILrVntbfurn78k1j2YNhoiGdjFFl5vUmJzEVWfa2 > 8L7ijaUpLue40HM3zIY/QS8N6IXykZ3iYQTsDwccwLk2sja/dwYxutaxs7T9fMVu > DckO3avg4xZBPOfvj5agmI7rOiLcRmOhcHmMvof4c+SV9B4EMj47RQtzXruGWdIR > mAzixcnHoxhhz32yoNiO3KeYVyP/KGGnB/e0l2N1GOnjViT0Y+Re0ilRYml/9Z6B > wnvXy1CcMr7tIVcEbGGdh16pziXSBo/kB2GWpprgDar7r1s6Ga/anGP7NL2GoLrF > 5ETaBZHqgfJGD0/RgnVy5NZC+E4WwWxFEPS3O1h1NLuvUyjdoUA0XZBoZVIDmvgz > bZjrTnIqp01L6PBcnl4+E+E9xAYQVWY1zzgHHVzCdKxw/xPPWmgHlkSwFlHr+4es > Y06SR5bK2ezQDykiObFs/P0dIv8K1mgFdU7YPc/IYYqH7PznzR90T616B4jvQuSc > Hg/R2ybFQqPPfHScT5XXdH7Ws1a0u4lqSs9jt0zu6xEpT2seDzJW3spkEnNphM6R > bycyI0J7yU9pfUHP9XmbbyoQUjIMHuiA0ZBFPx5DTNP7Ij6JiPlMR4oSBxVDjayu > vkk+I+HN8VlgcOeELQhAB34Tzs39kZTY6IAAutiavelsFmq+XBVNdHyli25oiARj > /Ozbk0FHiWuNDdVs4shTtSVUkKRGuAFyDTymjSNKvmtIwtOLI53ok1JJA/yOu9kg > 6Nen2L0mVHSl4JDkSYVuM20k7wKnfT5vZjbikbIaXrNwQFXki3Mz1QQcivQvzEp4 > kYge36a96eqN6ECJmk+3iy/+gwfoCr8V65eI6oWW5NUi27ox8P2kQz9RBvNYo0gi > ZV3JzAWDpuZWJSSL//4i > =feb5 > -----END PGP SIGNATURE----- > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/a9cf487a/attachment.html> From greg.hellings at gmail.com Sun Jan 20 14:02:50 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Sun, 20 Jan 2013 15:02:50 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: <CAHxvOVJn801uJ_+XeT2SxAw98mzUwbTL6cKyRvPZkUTPb6z2xw@mail.gmail.com> References: <50FAC626.3000304@crosswire.org> <CAHxvOVJn801uJ_+XeT2SxAw98mzUwbTL6cKyRvPZkUTPb6z2xw@mail.gmail.com> Message-ID: <CAHxvOVLrZ+dhQtg4W3+DP7=EGP_4XCKXCWMM9Gwq3KK=1CfzQw@mail.gmail.com> On Sun, Jan 20, 2013 at 1:28 PM, Greg Hellings <greg.hellings at gmail.com>wrote: > > > > On Sat, Jan 19, 2013 at 10:13 AM, Troy A. Griffitts <scribe at crosswire.org>wrote: > >> In anticipation of a new release, I have a large checkin I'm about to >> commit which will break everything for everyone compiling with -Werror. >> >> We've been normalizing method names toward a clean API interface at 2.0. >> SWORD started 20+ years ago when there was not standard naming >> conventions. In fact, originally we tried to keep variable names less than >> 8 characters, as, at the time, some compilers stopped disambiguating after >> this. Besides these, there are a number of conventions we used back then >> for which standards have now become the norm: camelCase conventions, >> standard set/getProperty naming, and the like. We've been slowly moving >> toward these changes and have been deprecating old names for a few years >> now. What I'm about to introduces standard names for all methods within >> the SWKey and SWModule classes and deprecates the non standard names. >> >> A few not obvious changes: >> >> Headings() has been renamed to setIntros(bool) and bool isIntros() >> Headings() -- used to turn on chapter, book, testament, and module >> introductions, has frequently been a point of confusion with the global >> option "Headings" -- used to turn on and off section headings in the text. >> This new property name will hopefully remove that confusion. >> >> Error() has become popError(), as the functionality has always been to >> return and clear any error code for the object. >> >> The bindings are probably in a state of disarray now. I've updated the >> omniorb bindings. I'd appreciated any help with other stuff. > > Additionally, BibleTime's sword-svn-compat branch has been updated to build cleanly against this, (excluding the unused variables message I mentioned in the other thread). --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130120/337cae0d/attachment-0001.html> From benpmorgan at gmail.com Sun Jan 20 16:30:15 2013 From: benpmorgan at gmail.com (Ben Morgan) Date: Mon, 21 Jan 2013 10:30:15 +1100 Subject: [sword-devel] Method Name Normalization In-Reply-To: <CAHxvOVJn801uJ_+XeT2SxAw98mzUwbTL6cKyRvPZkUTPb6z2xw@mail.gmail.com> References: <50FAC626.3000304@crosswire.org> <CAHxvOVJn801uJ_+XeT2SxAw98mzUwbTL6cKyRvPZkUTPb6z2xw@mail.gmail.com> Message-ID: <CA+2bjZLGGVKQvyZvBAMAU28qqY58e3XML6-AG-=mfqG3g0XkyQ@mail.gmail.com> Hi Greg, On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings <greg.hellings at gmail.com>wrote: > > > > SWIG bindings now up-to-date. > > Bindings users, please holler if I removed things overzealously. > > I haven't tried it, but I believe that this will break BPBible for example. As the bindings are part of SWORD, I believe it makes sense to mirror the deprecations in the bindings somehow if possible, rather than ignoring the deprecated definitions. I know that's what e.g. wxPython does, but I'm not sure how it does it. Doing this will make it easier to support both SWORD 1.6 and SVN, which I think is desirable until a couple of versions down the road. God Bless, Ben ------------------------------------------------------------- For I have no pleasure in the death of anyone, declares the Lord God; so turn, and live.? Ezekiel 18:32 (ESV) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130121/aeaf54a9/attachment.html> From dfhmch at googlemail.com Mon Jan 21 01:28:40 2013 From: dfhmch at googlemail.com (David Haslam) Date: Mon, 21 Jan 2013 00:28:40 -0800 (PST) Subject: [sword-devel] Vertical whitespace In-Reply-To: <88779976-CE1C-4F94-B6B2-B685C3C25752@crosswire.org> References: <88779976-CE1C-4F94-B6B2-B685C3C25752@crosswire.org> Message-ID: <1358756920815-4651722.post@n4.nabble.com> Having myself observed such symptoms, I'd heartily second DM's plea for an improvement on this rendering problem. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Vertical-whitespace-tp4651708p4651722.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Mon Jan 21 04:11:05 2013 From: dfhmch at googlemail.com (David Haslam) Date: Mon, 21 Jan 2013 03:11:05 -0800 (PST) Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358107307823-4651673.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> Message-ID: <1358766665083-4651723.post@n4.nabble.com> Further information at http://www.ubuntu.com/devices/phone David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651723.html Sent from the SWORD Dev mailing list archive at Nabble.com. From niccarter at mac.com Mon Jan 21 04:28:25 2013 From: niccarter at mac.com (Nic Carter) Date: Mon, 21 Jan 2013 22:28:25 +1100 Subject: [sword-devel] Method Name Normalization In-Reply-To: <50FAC626.3000304@crosswire.org> References: <50FAC626.3000304@crosswire.org> Message-ID: <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> On 20/01/2013, at 3:13 AM, Troy A. Griffitts <scribe at crosswire.org> wrote: > Headings() has been renamed to setIntros(bool) and bool isIntros() > Headings() -- used to turn on chapter, book, testament, and module introductions, has frequently been a point of confusion with the global option "Headings" -- used to turn on and off section headings in the text. This new property name will hopefully remove that confusion. Is there a reason for this being the abbreviation and not "setIntroductions(bool)" and "isIntroductions()"? I find it strange that you've fixed up "Lang()" and introduced "Intros()"... But, thanks for this change. It was confusing before! :) Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) I say "think" cause it threw an error for me and then I realised I didn't need that in my stuff, so I simply deleted it rather than "fix" it... ;) Thanks for all of this. :) Still double checking it all with my stuff, but looking good so far :) Thanks, ybic nic... :) From scribe at crosswire.org Mon Jan 21 04:49:54 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Mon, 21 Jan 2013 12:49:54 +0100 Subject: [sword-devel] Method Name Normalization In-Reply-To: <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> References: <50FAC626.3000304@crosswire.org> <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> Message-ID: <50FD2B62.8000009@crosswire.org> On 01/21/2013 12:28 PM, Nic Carter wrote: > Is there a reason for this being the abbreviation and not > "setIntroductions(bool)" and "isIntroductions()"? I find it strange > that you've fixed up "Lang()" and introduced "Intros()"... But, thanks > for this change. It was confusing before! :) Yeah, well. :) Here was my thinking on this. No one says "Lang" as a spoken abbreviation for Language, but we all use "Intros" regularly. In fact-- seeking to justify my behavior-- it looks like google even claims "intro" as it's own word: https://www.google.com/search?q=definition+intro :) > Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) > I say "think" cause it threw an error for me and then I realised I > didn't need that in my stuff, so I simply deleted it rather than "fix" > it.. Fixed. Thanks for the heads up Nic. Troy > . ;) Thanks for all of this. :) Still double checking it all with my > stuff, but looking good so far :) Thanks, ybic nic... :) > _______________________________________________ sword-devel mailing > list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to > unsubscribe/change your settings at above page From israeldahl at gmail.com Mon Jan 21 05:51:01 2013 From: israeldahl at gmail.com (Israel) Date: Mon, 21 Jan 2013 06:51:01 -0600 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358766665083-4651723.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> Message-ID: <50FD39B5.6000708@gmail.com> I am new to the developers list here, and David has written about the whole reason I have joined. I have begun familiarizing myself with QML, the language the Ubuntu Phone apps are written in. I would like to begin work on a sword app for the Ubuntu Phone UI, and as such I thought I should subscribe here, so I can get help if I need it, and see if anyone is already working on that very same idea. -Israel On 01/21/2013 05:11 AM, David Haslam wrote: > Further information at http://www.ubuntu.com/devices/phone > > David > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651723.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -- Regards From chris at burrell.me.uk Mon Jan 21 06:10:49 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Mon, 21 Jan 2013 13:10:49 +0000 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <50FD39B5.6000708@gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> Message-ID: <CACQnaRUQYhQxqELVGyM3njVTytGZ+FB680edNaqrw91uku8mOA@mail.gmail.com> If Ubuntu phones eventually run Java, we (STEP) will be aiming for an app on that platform. Chris On 21 January 2013 12:51, Israel <israeldahl at gmail.com> wrote: > I am new to the developers list here, and David has written about the > whole reason I have joined. I have begun familiarizing myself with QML, > the language the Ubuntu Phone apps are written in. I would like to begin > work on a sword app for the Ubuntu Phone UI, and as such I thought I should > subscribe here, so I can get help if I need it, and see if anyone is > already working on that very same idea. > -Israel > > > On 01/21/2013 05:11 AM, David Haslam wrote: > >> Further information at http://www.ubuntu.com/devices/**phone<http://www.ubuntu.com/devices/phone> >> >> David >> >> >> >> -- >> View this message in context: http://sword-dev.350566.n4.** >> nabble.com/Trends-in-mobile-**platforms-tp4651673p4651723.**html<http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651723.html> >> Sent from the SWORD Dev mailing list archive at Nabble.com. >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> > > > -- > Regards > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130121/9a09848d/attachment-0001.html> From israeldahl at gmail.com Mon Jan 21 06:24:05 2013 From: israeldahl at gmail.com (Israel) Date: Mon, 21 Jan 2013 07:24:05 -0600 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <CACQnaRUQYhQxqELVGyM3njVTytGZ+FB680edNaqrw91uku8mOA@mail.gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> <CACQnaRUQYhQxqELVGyM3njVTytGZ+FB680edNaqrw91uku8mOA@mail.gmail.com> Message-ID: <50FD4175.9090900@gmail.com> @Chris Burrell You can integrate Java into QML directly. http://doc.qt.digia.com/4.7-snapshot/qdeclarativejavascript.html HTML5 and QML are the languages to use for native phone apps... no doubt a java app could run in some form, because the whole GNU/Linux OS is on the phone, but it is seems that they do not want to use Java only apps. http://developer.ubuntu.com/get-started/gomobile/ On 01/21/2013 07:10 AM, Chris Burrell wrote: > If Ubuntu phones eventually run Java, we (STEP) will be aiming for an > app on that platform. > Chris From raoul at snyman.info Mon Jan 21 06:26:37 2013 From: raoul at snyman.info (Raoul Snyman) Date: Mon, 21 Jan 2013 13:26:37 +0000 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <50FD4175.9090900@gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> <CACQnaRUQYhQxqELVGyM3njVTytGZ+FB680edNaqrw91uku8mOA@mail.gmail.com> <50FD4175.9090900@gmail.com> Message-ID: <2e963471331c75004f6aea254e70e9dd@localhost> On Mon, 21 Jan 2013 07:24:05 -0600, Israel wrote: > You can integrate Java into QML directly. > http://doc.qt.digia.com/4.7-snapshot/qdeclarativejavascript.html JavaScript != Java. -- Raoul Snyman, B.Tech IT (Software Engineering) m: 082 550 3754 e: raoul at snyman.info w: http://snyman.info/ From greg.hellings at gmail.com Mon Jan 21 06:28:48 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 21 Jan 2013 07:28:48 -0600 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <50FD39B5.6000708@gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> Message-ID: <CAHxvOV+kLgz=_2Rfza=u8K-gFKqMZS4qfjzU1w4SETz=MDUP=w@mail.gmail.com> If QML refers to the methods and libraries, etc used by Qt development, then your work would integrate well with BibleTime. Our application is written in Qt and we would like to eventually separate the lower half of our application from the presentation layer so that we can target multiple form-factors of applications from a shared code base that would handle direct interaction with the SWORD code. --Greg On Mon, Jan 21, 2013 at 6:51 AM, Israel <israeldahl at gmail.com> wrote: > I am new to the developers list here, and David has written about the > whole reason I have joined. I have begun familiarizing myself with QML, > the language the Ubuntu Phone apps are written in. I would like to begin > work on a sword app for the Ubuntu Phone UI, and as such I thought I should > subscribe here, so I can get help if I need it, and see if anyone is > already working on that very same idea. > -Israel > > > On 01/21/2013 05:11 AM, David Haslam wrote: > >> Further information at http://www.ubuntu.com/devices/**phone<http://www.ubuntu.com/devices/phone> >> >> David >> >> >> >> -- >> View this message in context: http://sword-dev.350566.n4.** >> nabble.com/Trends-in-mobile-**platforms-tp4651673p4651723.**html<http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651723.html> >> Sent from the SWORD Dev mailing list archive at Nabble.com. >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> > > > -- > Regards > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel<http://www.crosswire.org/mailman/listinfo/sword-devel> > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130121/54334a62/attachment.html> From israeldahl at gmail.com Mon Jan 21 06:29:13 2013 From: israeldahl at gmail.com (Israel) Date: Mon, 21 Jan 2013 07:29:13 -0600 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <2e963471331c75004f6aea254e70e9dd@localhost> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> <CACQnaRUQYhQxqELVGyM3njVTytGZ+FB680edNaqrw91uku8mOA@mail.gmail.com> <50FD4175.9090900@gmail.com> <2e963471331c75004f6aea254e70e9dd@localhost> Message-ID: <50FD42A9.80104@gmail.com> On 01/21/2013 07:26 AM, Raoul Snyman wrote: > On Mon, 21 Jan 2013 07:24:05 -0600, Israel wrote: >> You can integrate Java into QML directly. >> http://doc.qt.digia.com/4.7-snapshot/qdeclarativejavascript.html > JavaScript != Java. > > Ah... well shows what I know about Java and Javascript.... -- Regards From israeldahl at gmail.com Mon Jan 21 06:42:53 2013 From: israeldahl at gmail.com (Israel) Date: Mon, 21 Jan 2013 07:42:53 -0600 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <CAHxvOV+kLgz=_2Rfza=u8K-gFKqMZS4qfjzU1w4SETz=MDUP=w@mail.gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> <50FD39B5.6000708@gmail.com> <CAHxvOV+kLgz=_2Rfza=u8K-gFKqMZS4qfjzU1w4SETz=MDUP=w@mail.gmail.com> Message-ID: <50FD45DD.6090702@gmail.com> Yes you are correct about QML and Qt. Your program could potentially be rewritten to use a QML face when the phone is in "Phone UI" mode, and then revert to the current "desktop" face when the phone was docked, possibly... though I don't understand how the UI switches from the Qt Phone UI to the regular Unity UI when it is docked. I will get your source code and start looking at it... should I just use the source from the Ubuntu repos, or is there an upstream somewhere that is more current? On 01/21/2013 07:28 AM, Greg Hellings wrote: > If QML refers to the methods and libraries, etc used by Qt > development, then your work would integrate well with BibleTime. Our > application is written in Qt and we would like to eventually separate > the lower half of our application from the presentation layer so that > we can target multiple form-factors of applications from a shared code > base that would handle direct interaction with the SWORD code. > > --Greg > > > On Mon, Jan 21, 2013 at 6:51 AM, Israel <israeldahl at gmail.com > <mailto:israeldahl at gmail.com>> wrote: > > I am new to the developers list here, and David has written about > the whole reason I have joined. I have begun familiarizing myself > with QML, the language the Ubuntu Phone apps are written in. I > would like to begin work on a sword app for the Ubuntu Phone UI, > and as such I thought I should subscribe here, so I can get help > if I need it, and see if anyone is already working on that very > same idea. > -Israel > > > On 01/21/2013 05:11 AM, David Haslam wrote: > > Further information at http://www.ubuntu.com/devices/phone > > David > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651723.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > <mailto:sword-devel at crosswire.org> > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > -- > Regards > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > <mailto:sword-devel at crosswire.org> > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -- Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130121/b34cf0e4/attachment-0001.html> From refdoc at gmx.net Mon Jan 21 07:23:08 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Mon, 21 Jan 2013 15:23:08 +0100 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> Message-ID: <20130121142308.208110@gmx.net> > Von: DM Smith <dmsmith at crosswire.org> > In the past, I've viewed the "headings" toggle as a toggle for > non-canonical material. But the discussion on the other thread has me wondering > whether intros (non-canonical) information is handled by it. > That is exactly what I said - the headline toggle switches on everything, intros and the like. Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. Peter From scribe at crosswire.org Mon Jan 21 08:07:35 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Mon, 21 Jan 2013 16:07:35 +0100 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <20130121142308.208110@gmx.net> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> Message-ID: <50FD59B7.5020907@crosswire.org> OK, to clear this up technically. setIntros() turns on and off the versification extra 'slots': TSTMT BK CH:0 - chapter intro TSTMT BK 0:0 - book intro TSTMT 0 0:0 - testament intro 0 0 0:0 - module intro This has nothing to do with filtering tagged content (In the engine) __________________________________________ setGlobalOption("Headings", "On"|"Off") This will tell the filter set to turn on/off showing anything considered a section heading. This used to only be pre-verse titles (e.g., "The Sermon On The Mount")-- as DM has pointed out. (Relatively) Recent changes have expanded this to be any content 'pre-verse'-- not just stuff in a <title> tag. I can see conceptually how these can easily get blurred. It was much easier to see the difference when "Headings" was limited to titles like "The Sermon On The Mount". I don't like seeing these when I am reading through the text. They are sometimes like "spoilers" in a movie, e.g., "The Death of King Saul" I usually turn these off when I am reading. On the other hand, when I am flipping through my printed Bible, I value these to help orient me to about where I am. Intros were seen as lengthy book or chapter introductions frequent in printed study Bibles. Now that "pre-verse" material can be lengthier than simply a section heading, it does blur the lines a little. Anyway, just wanted to technical state the difference between the two mechanisms. Troy On 01/21/2013 03:23 PM, Peter von Kaehne wrote: >> Von: DM Smith <dmsmith at crosswire.org> >> In the past, I've viewed the "headings" toggle as a toggle for >> non-canonical material. But the discussion on the other thread has me wondering >> whether intros (non-canonical) information is handled by it. >> > That is exactly what I said - the headline toggle switches on everything, intros and the like. > > Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. > > Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? > > FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. > > Peter > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From mcepl at redhat.com Mon Jan 21 08:56:36 2013 From: mcepl at redhat.com (=?UTF-8?B?TWF0xJtqIENlcGw=?=) Date: Mon, 21 Jan 2013 16:56:36 +0100 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358107307823-4651673.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> Message-ID: <50FD6534.4010109@redhat.com> On 13/01/13 21:01, David Haslam wrote: > Two recent announcements about mobile platforms caught my attention. These > were timed to make the headlines during the CES 2013 in Las Vegas. > > 1. The advent of *Ubuntu Phone* (formerly Ubuntu Mobile) as an alternative > to Android OS. > 2. The prospect of *Firefox OS* based mobile & tablet devices based on > HTML5. > > With these in mind, it should prompt thoughts by front-end developers as to > the opportunities with these platforms for developing new SWORD or JSword > based Bible study applications, or possibly adapting one or more of our > existing ones. If I understand correctly, then Ubuntu Phone will support HTML5 webapps-as-apps as well, so if we write HTML5-app we shoot two birds with one stone so to say. Besides, if I would be asked about my bets Ubuntu Phone v. Firefox OS, I would certainly bet on the latter (they have real and multiple phone manufacturers, real phone operators supporting them; the former has none of these things). My ?0.02 (or CZK0.02, if you want to be cheap). Mat?j From dfhmch at googlemail.com Mon Jan 21 09:34:41 2013 From: dfhmch at googlemail.com (David Haslam) Date: Mon, 21 Jan 2013 08:34:41 -0800 (PST) Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358107307823-4651673.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> Message-ID: <1358786081748-4651736.post@n4.nabble.com> See also http://en.wikipedia.org/wiki/Firefox_OS David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651736.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dmsmith at crosswire.org Mon Jan 21 09:37:40 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 21 Jan 2013 11:37:40 -0500 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <20130121142308.208110@gmx.net> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> Message-ID: <F798CEF3-5010-46B3-B938-89EA10C1F332@crosswire.org> On Jan 21, 2013, at 9:23 AM, "Peter von Kaehne" <refdoc at gmx.net> wrote: > >> Von: DM Smith <dmsmith at crosswire.org> > >> In the past, I've viewed the "headings" toggle as a toggle for >> non-canonical material. But the discussion on the other thread has me wondering >> whether intros (non-canonical) information is handled by it. >> > > That is exactly what I said - the headline toggle switches on everything, intros and the like. > > Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. > > Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? Here is what osis2mod expects regarding intros and headings. Intro to the work as a whole: not expected, and not handled. Intro to a testament: not expected, not handled. These intros are not ignored, but accumulated for the first write done by osis2mod. Hopefully it will be a book intro, but the behavior is not defined. Intro to a book. This is everything between <div type="book"> and <chapter> (or <div type="chapter">, the other chapter start). Intro to a chapter. This is a bit more difficult. The problem is that it occupies the space between a chapter start and verse 1. These may be a chapter title, or verse title, or both. Osis2mod uses markup help to distinguish these. Here are the rules: o If the <title> is within <div type="section"> it is understood as a verse title. o If the <title> has a type other than main, chapter or sub, it is understood as a verse title. Note, the first of these conditions determines a boundary between chapter and verse. If after one of these there is a title that has a type of main, chapter or sub. It is understood as belonging to the verse, not the chapter. That is how the title element is decided. > > FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. Note, when the chapter start is seen an inChapterIntro is set. And when one of the above is met, then inChapterIntro is cleared and inPreVerse is set. So, the div type of intro is not directly taken into account. There is another part to preVerse determination: whether interVerse material falls with verse n (where n >= 1) or verse n+1. (This does not apply to the division between chapter start and first verse). Basically, after the </verse> (or equivalent) is found it looks for start, end and empty tags. As long as end and empty tags are found, it is seen as belonging to the prior verse. Otherwise it is seen as the next verse. This applies to the division between chapter and first verse and to one verse and the next. But it does not apply to stuff after the last verse of the chapter (such as colophons). That is appended to the last verse. Hope this helps. In Him, DM From christopher at burrell.me.uk Mon Jan 21 09:44:51 2013 From: christopher at burrell.me.uk (Chris Burrell) Date: Mon, 21 Jan 2013 16:44:51 +0000 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358786081748-4651736.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358786081748-4651736.post@n4.nabble.com> Message-ID: <CACQnaRXkdxpHmHYGJHNmF3zYQ6=sigdP3Dg-QAVLO+inEbrHig@mail.gmail.com> I thought the whole point of the Ubuntu phone OS is that it ran a full-blown OS... In which won't every front-end theoritically run on it. Chris On 21 January 2013 16:34, David Haslam <dfhmch at googlemail.com> wrote: > See also http://en.wikipedia.org/wiki/Firefox_OS > > David > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Trends-in-mobile-platforms-tp4651673p4651736.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130121/dad62a1c/attachment.html> From dmsmith at crosswire.org Mon Jan 21 09:52:20 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 21 Jan 2013 11:52:20 -0500 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <50FD59B7.5020907@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> Message-ID: <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> On Jan 21, 2013, at 10:07 AM, "Troy A. Griffitts" <scribe at crosswire.org> wrote: > OK, to clear this up technically. > > setIntros() turns on and off the versification extra 'slots': > > TSTMT BK CH:0 - chapter intro > TSTMT BK 0:0 - book intro > TSTMT 0 0:0 - testament intro > 0 0 0:0 - module intro As noted, not all these are handled by osis2mod, but only book and chapter intros. Someday, I'd like direction to add module and testament intros. > > This has nothing to do with filtering tagged content (In the engine) > __________________________________________ > > setGlobalOption("Headings", "On"|"Off") > > This will tell the filter set to turn on/off showing anything considered a section heading. This used to only be pre-verse titles (e.g., "The Sermon On The Mount")-- as DM has pointed out. (Relatively) Recent changes have expanded this to be any content 'pre-verse'-- not just stuff in a <title> tag. This is a problem. It should not toggle the entire pre-verse div, but only the titles (title element and its content) and other text (presumably non-canonical) contained in it. It should not filter the structural tags. The filtering of those structural tags is the problem mentioned in the thread "Vertical Whitespace." > > I can see conceptually how these can easily get blurred. It was much easier to see the difference when "Headings" was limited to titles like "The Sermon On The Mount". I don't like seeing these when I am reading through the text. They are sometimes like "spoilers" in a movie, e.g., "The Death of King Saul" I usually turn these off when I am reading. On the other hand, when I am flipping through my printed Bible, I value these to help orient me to about where I am. Intros were seen as lengthy book or chapter introductions frequent in printed study Bibles. Now that "pre-verse" material can be lengthier than simply a section heading, it does blur the lines a little. I'm still confused. When verse 0 is requested (regardless of what type of intro it is), Peter notes that it is affected by the headings render filter. I'm pretty sure that the material in it is not marked pre-verse. It seems to me that verse 0 is always non-canonical and should be toggled by a "not canonical" render filter. > > Anyway, just wanted to technical state the difference between the two mechanisms. > > Troy > > > > > > On 01/21/2013 03:23 PM, Peter von Kaehne wrote: >>> Von: DM Smith <dmsmith at crosswire.org> >>> In the past, I've viewed the "headings" toggle as a toggle for >>> non-canonical material. But the discussion on the other thread has me wondering >>> whether intros (non-canonical) information is handled by it. >>> >> That is exactly what I said - the headline toggle switches on everything, intros and the like. >> >> Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. >> >> Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? >> >> FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. >> >> Peter >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From refdoc at gmx.net Mon Jan 21 10:21:18 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Mon, 21 Jan 2013 18:21:18 +0100 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> Message-ID: <20130121172118.73320@gmx.net> > Von: DM Smith <dmsmith at crosswire.org> > As noted, not all these are handled by osis2mod, but only book and chapter > intros. Someday, I'd like direction to add module and testament intros. Right now, my impression is that none of these are handled correctly. Please point at a single module which deals with this correctly. I know none. All of them switch intros on and off together with headlines. Leaving this aside, the "0" convention is not covering the case of section intros. FWIW how I would like to see things is following: (1)Text related title toggle (2)Explanatory material toggle - and that can and should include both the current "0" material and intersection etc material. And at former may well have titles which need to go on only when explanatory material is toggled on, while latter does not work without (1) So, both switches are dependent on each other in some form. Peter From dmitrij.ledkov at ubuntu.com Mon Jan 21 10:44:31 2013 From: dmitrij.ledkov at ubuntu.com (Dmitrijs Ledkovs) Date: Mon, 21 Jan 2013 17:44:31 +0000 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <CACQnaRXkdxpHmHYGJHNmF3zYQ6=sigdP3Dg-QAVLO+inEbrHig@mail.gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358786081748-4651736.post@n4.nabble.com> <CACQnaRXkdxpHmHYGJHNmF3zYQ6=sigdP3Dg-QAVLO+inEbrHig@mail.gmail.com> Message-ID: <CANBHLUhd7B5mWZqrLR_p4jxaJB294zOUXwM7xVu1-bsbSGm89A@mail.gmail.com> On 21 January 2013 16:44, Chris Burrell <christopher at burrell.me.uk> wrote: > > I thought the whole point of the Ubuntu phone OS is that it ran a > full-blown OS... In which won't every front-end theoritically run on it. > When docked, yes you get full ubuntu unity desktop. But when not-docked, i.e. touch screen mode. The supported SDK/UI are Webapps or Qt 5 / QML with specific ubuntu phone touch UI components. For further details on Ubuntu Phone SDK see: http://developer.ubuntu.com/get-started/gomobile/ Regards, Dmitrijs. From scribe at crosswire.org Mon Jan 21 10:52:13 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Mon, 21 Jan 2013 18:52:13 +0100 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> Message-ID: <50FD804D.7000304@crosswire.org> On 01/21/2013 05:52 PM, DM Smith wrote: > On Jan 21, 2013, at 10:07 AM, "Troy A. Griffitts" <scribe at crosswire.org> wrote: > >> OK, to clear this up technically. >> >> setIntros() turns on and off the versification extra 'slots': >> >> TSTMT BK CH:0 - chapter intro >> TSTMT BK 0:0 - book intro >> TSTMT 0 0:0 - testament intro >> 0 0 0:0 - module intro > As noted, not all these are handled by osis2mod, but only book and chapter intros. Someday, I'd like direction to add module and testament intros. > >> This has nothing to do with filtering tagged content (In the engine) >> __________________________________________ >> >> setGlobalOption("Headings", "On"|"Off") >> >> This will tell the filter set to turn on/off showing anything considered a section heading. This used to only be pre-verse titles (e.g., "The Sermon On The Mount")-- as DM has pointed out. (Relatively) Recent changes have expanded this to be any content 'pre-verse'-- not just stuff in a <title> tag. > This is a problem. It should not toggle the entire pre-verse div, but only the titles (title element and its content) and other text (presumably non-canonical) contained in it. It should not filter the structural tags. The filtering of those structural tags is the problem mentioned in the thread "Vertical Whitespace." What do you envision in the inter-verse material which should be displayed? Newlines? Is this the only thing that prevents toggling preverse material based on the "Headings" option? I'm not arguing one way or another (yet). I'm just interested. The previous "purpose" for the "preverse" material concept was to isolate material which should be shown when a verse is being viewed in context, but which needs to be shown before the verse marker. There are many use cases for this need. One is: When the verse is being shown stand-along (e.g., in a search results list) this material is (typically) not shown by a frontend. Another is: Many users which to turn this material off when reading in context. Until recently, the only thing in this space was section headings., so turning on and off pre-verse material based on section headings made sense. What kinds of things would you still want to be shown when sections headings are turned off? >> I can see conceptually how these can easily get blurred. It was much easier to see the difference when "Headings" was limited to titles like "The Sermon On The Mount". I don't like seeing these when I am reading through the text. They are sometimes like "spoilers" in a movie, e.g., "The Death of King Saul" I usually turn these off when I am reading. On the other hand, when I am flipping through my printed Bible, I value these to help orient me to about where I am. Intros were seen as lengthy book or chapter introductions frequent in printed study Bibles. Now that "pre-verse" material can be lengthier than simply a section heading, it does blur the lines a little. > I'm still confused. When verse 0 is requested (regardless of what type of intro it is), Peter notes that it is affected by the headings render filter. I'm pretty sure that the material in it is not marked pre-verse. Material in the intro slots of the versification are not affected by setGlobalOption("Headings", "On"|"Off"). Let me say it differently: the fact that material is in an intro slot in the versification has no bearing on how the "Heading" option filters work. This materal might all be marked by something the "Headings" filters will remove (right or wrong), but it does not remove them based on them being in a 0 slot. > > It seems to me that verse 0 is always non-canonical and should be toggled by a "not canonical" render filter. Renaming a feature from "Toggle Section Headings" to "Toggle Non-canonical" might make more sense to us, and indeed may do exactly what the user intends, but will they understand the feature title? Should we keep the feature title the same but act as "Toggle Non-canonical"? Hmmm. Maybe, but might there be other stuff the user wants to see that's non-canonical? Footnotes? x-refs, "Intros" :) Just thinking out loud right now. Troy >> Anyway, just wanted to technical state the difference between the two mechanisms. >> >> Troy >> >> >> >> >> >> On 01/21/2013 03:23 PM, Peter von Kaehne wrote: >>>> Von: DM Smith <dmsmith at crosswire.org> >>>> In the past, I've viewed the "headings" toggle as a toggle for >>>> non-canonical material. But the discussion on the other thread has me wondering >>>> whether intros (non-canonical) information is handled by it. >>>> >>> That is exactly what I said - the headline toggle switches on everything, intros and the like. >>> >>> Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. >>> >>> Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? >>> >>> FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. >>> >>> Peter >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dfhmch at googlemail.com Mon Jan 21 13:13:17 2013 From: dfhmch at googlemail.com (David Haslam) Date: Mon, 21 Jan 2013 12:13:17 -0800 (PST) Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <50FD804D.7000304@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> <50FD804D.7000304@crosswire.org> Message-ID: <1358799197066-4651743.post@n4.nabble.com> From bogus@does.not.exist.com Wed Jan 16 06:18:08 2013 From: bogus@does.not.exist.com () Date: Wed, 16 Jan 2013 13:18:08 -0000 Subject: No subject Message-ID: <mailman.0.1358799427.6807.sword-devel@crosswire.org> When canonical="true", it means that the content of that element is a part of the text being encoded. For example, the "text" of the Bible includes the content of books, chapters, and verses but does not include notes, section-headings added by editors or translators, etc. Therefore, the default value for elements such as note is false, as the content of that element has been added by an editor or author to the text being encoded. /It should be explicitly noted that the value of the canonical attribute should not be used to reflect theological judgment about the content of a text, but merely to distinguish between what has been added to the text and what has not./ I'm citing this merely as a reminder, since newcomers to this list may not fully appreciate what this attribute is for. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Pre-verse-div-and-headings-tp4651710p4651743.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Mon Jan 21 13:22:22 2013 From: dfhmch at googlemail.com (David Haslam) Date: Mon, 21 Jan 2013 12:22:22 -0800 (PST) Subject: [sword-devel] On the topic of patches to SWORD .... Message-ID: <1358799742173-4651744.post@n4.nabble.com> There being a number of ongoing email threads about patches, it may be convenient for programmers to be reminded of the cool feature in *xulsword* regarding dictionary/glossary links. Please refer to http://crosswire.org/wiki/Talk:DevTools:conf_Files#Suggestion_for_new_OSIS_filter_to_toggle_the_appearance_and_activeness_of_dictionary_lookup_links The patch should be relatively simple to apply to the SWORD API, and we can readily update the wiki page about .conf files <http://crosswire.org/wiki/DevTools:conf_Files> . David -- View this message in context: http://sword-dev.350566.n4.nabble.com/On-the-topic-of-patches-to-SWORD-tp4651744.html Sent from the SWORD Dev mailing list archive at Nabble.com. From karl at kleinpaste.org Mon Jan 21 14:42:37 2013 From: karl at kleinpaste.org (Karl Kleinpaste) Date: Mon, 21 Jan 2013 16:42:37 -0500 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <20130121172118.73320@gmx.net> (Peter von Kaehne's message of "Mon, 21 Jan 2013 18:21:18 +0100") References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> <20130121172118.73320@gmx.net> Message-ID: <vxk622qtdpu.fsf@awol.kleinpaste.org> Xiphos displays 0:0 and n:0 intro material based on the user's single per-module setting for headings. It's not because of the engine; it's because that's how the handling of getting the boundary verse before the current chapter is handled. From mcepl at redhat.com Mon Jan 21 14:44:05 2013 From: mcepl at redhat.com (=?UTF-8?B?TWF0xJtqIENlcGw=?=) Date: Mon, 21 Jan 2013 22:44:05 +0100 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <CANBHLUhd7B5mWZqrLR_p4jxaJB294zOUXwM7xVu1-bsbSGm89A@mail.gmail.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358786081748-4651736.post@n4.nabble.com> <CACQnaRXkdxpHmHYGJHNmF3zYQ6=sigdP3Dg-QAVLO+inEbrHig@mail.gmail.com> <CANBHLUhd7B5mWZqrLR_p4jxaJB294zOUXwM7xVu1-bsbSGm89A@mail.gmail.com> Message-ID: <50FDB6A5.7040009@redhat.com> On 21/01/13 18:44, Dmitrijs Ledkovs wrote: > But when not-docked, i.e. touch screen mode. The supported SDK/UI are > Webapps or Qt 5 / QML with specific ubuntu phone touch UI components. And just to add one more reasons why I believe Ubuntu Phone is DOA ... notice Qt 5. Mark Shuttleworth was sounding in the Ubuntu Phone PR video that these are just different UIs for the same OS. Except it is not true ... all those Gtk applications which currently run on plain Ubuntu need to be completely rewritten to the new framework (and yes, those new apps could run both on desktop and phone, but complete rewrite of apps is required). Mat?j From benpmorgan at gmail.com Mon Jan 21 15:02:07 2013 From: benpmorgan at gmail.com (Ben Morgan) Date: Tue, 22 Jan 2013 09:02:07 +1100 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <vxk622qtdpu.fsf@awol.kleinpaste.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> <20130121172118.73320@gmx.net> <vxk622qtdpu.fsf@awol.kleinpaste.org> Message-ID: <CA+2bjZK7xhAja=VwKp8gRNLNJfPTtH8+LOumNGTsiS22fZ93mg@mail.gmail.com> If I remember correctly BPBible's headings option turns off non-canonical headings. When rendering text, vk.Headings()/setIntros() would always be on. There's no way to turn off prechapter content, just like there's no way to turn off every verse 5 [?] (if it doesn't work this way in some situations, I think it should as I believe this is the desired mode of operation) God Bless, Ben ------------------------------------------------------------- For I have no pleasure in the death of anyone, declares the Lord God; so turn, and live.? Ezekiel 18:32 (ESV) On Tue, Jan 22, 2013 at 8:42 AM, Karl Kleinpaste <karl at kleinpaste.org>wrote: > Xiphos displays 0:0 and n:0 intro material based on the user's single > per-module setting for headings. It's not because of the engine; it's > because that's how the handling of getting the boundary verse before the > current chapter is handled. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130122/59faa020/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 330.gif Type: image/gif Size: 96 bytes Desc: not available URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130122/59faa020/attachment.gif> From dmsmith at crosswire.org Mon Jan 21 15:04:07 2013 From: dmsmith at crosswire.org (DM Smith) Date: Mon, 21 Jan 2013 17:04:07 -0500 Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <50FD804D.7000304@crosswire.org> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> <50FD804D.7000304@crosswire.org> Message-ID: <CAD2AD8F-55D5-49C9-A244-FC6676FBE057@crosswire.org> On Jan 21, 2013, at 12:52 PM, "Troy A. Griffitts" <scribe at crosswire.org> wrote: > On 01/21/2013 05:52 PM, DM Smith wrote: >> On Jan 21, 2013, at 10:07 AM, "Troy A. Griffitts" <scribe at crosswire.org> wrote: >> >>> OK, to clear this up technically. >>> >>> setIntros() turns on and off the versification extra 'slots': >>> >>> TSTMT BK CH:0 - chapter intro >>> TSTMT BK 0:0 - book intro >>> TSTMT 0 0:0 - testament intro >>> 0 0 0:0 - module intro >> As noted, not all these are handled by osis2mod, but only book and chapter intros. Someday, I'd like direction to add module and testament intros. >> >>> This has nothing to do with filtering tagged content (In the engine) >>> __________________________________________ >>> >>> setGlobalOption("Headings", "On"|"Off") Well, Karl's post clears up why this works. From my best recollection the material in verse 0 is not marked as pre-verse. The headings filter does not filter verse 0. So the app has to. >>> >>> This will tell the filter set to turn on/off showing anything considered a section heading. This used to only be pre-verse titles (e.g., "The Sermon On The Mount")-- as DM has pointed out. (Relatively) Recent changes have expanded this to be any content 'pre-verse'-- not just stuff in a <title> tag. >> This is a problem. It should not toggle the entire pre-verse div, but only the titles (title element and its content) and other text (presumably non-canonical) contained in it. It should not filter the structural tags. The filtering of those structural tags is the problem mentioned in the thread "Vertical Whitespace." > > What do you envision in the inter-verse material which should be displayed? Newlines? Yes. Exactly. In the "Vertical Whitespace" post, I outlined how they should be displayed. > Is this the only thing that prevents toggling preverse material based on the "Headings" option? I'm not sure what you mean by "prevents." I think that for Bibles, the only text between verses that should be displayed regardless of the toggle are titles marked canonical="true". But I don't mind if titles and introductory material is handled by cooperating toggles. > > I'm not arguing one way or another (yet). I'm just interested. The previous "purpose" for the "preverse" material concept was to isolate material which should be shown when a verse is being viewed in context, but which needs to be shown before the verse marker. There are many use cases for this need. One is: > > When the verse is being shown stand-along (e.g., in a search results list) this material is (typically) not shown by a frontend. Right. The corollary of this is when verses are shown one per line. This is asking for much of the structural formatting to be ignored. Not sure how much should be kept. > > Another is: > > Many users which to turn this material off when reading in context. Yes. Part of the context is paragraphing. Part of the context is proper indentation of poetry (or what has been formatted as such). Most paragraphing and poetry markup is between verses. > > Until recently, the only thing in this space was section headings., so turning on and off pre-verse material based on section headings made sense. Right. > > What kinds of things would you still want to be shown when sections headings are turned off? New lines and also indents (for poetry based on the level (?) attribute.) So both vertical and horizontal whitespace. Again, I don't mind if intros are handled independently from titles. > >>> I can see conceptually how these can easily get blurred. It was much easier to see the difference when "Headings" was limited to titles like "The Sermon On The Mount". I don't like seeing these when I am reading through the text. They are sometimes like "spoilers" in a movie, e.g., "The Death of King Saul" I usually turn these off when I am reading. On the other hand, when I am flipping through my printed Bible, I value these to help orient me to about where I am. Intros were seen as lengthy book or chapter introductions frequent in printed study Bibles. Now that "pre-verse" material can be lengthier than simply a section heading, it does blur the lines a little. >> I'm still confused. When verse 0 is requested (regardless of what type of intro it is), Peter notes that it is affected by the headings render filter. I'm pretty sure that the material in it is not marked pre-verse. > Material in the intro slots of the versification are not affected by setGlobalOption("Headings", "On"|"Off"). > Let me say it differently: the fact that material is in an intro slot in the versification has no bearing on how the "Heading" option filters work. This materal might all be marked by something the "Headings" filters will remove (right or wrong), but it does not remove them based on them being in a 0 slot. > > >> >> It seems to me that verse 0 is always non-canonical and should be toggled by a "not canonical" render filter. > > Renaming a feature from "Toggle Section Headings" to "Toggle Non-canonical" might make more sense to us, and indeed may do exactly what the user intends, but will they understand the feature title? Should we keep the feature title the same but act as "Toggle Non-canonical"? Hmmm. Maybe, but might there be other stuff the user wants to see that's non-canonical? Footnotes? x-refs, "Intros" :) Just thinking out loud right now. Footnotes are clearly not canonical and they have their own toggle. I think the same is true for x-refs. And we have a toggle for headings. But it is really not a headings toggle today. It is a pre-verse toggle. Which was the only expected place for headings. But no toggle for intro. Unless it is also part of the headings toggle (as Karl says is done w/in Xiphos, not the engine.) There is another headings scenario that others have brought up. The title that splits a verse. I think that there have been some sightings in the wild. In this scenario we have something like the following (indentation and newlines for clarity). I've also included section introductions which one might find in a study Bible: <verse osisID="Book.x.y" sID="Book.x.y"/> First part of the verse text. </div> <!-- end of prior section --> <div type="section" canonical="true"> <title>Section title

First paragraph of section introduction

Second paragraph of section introduction

Second part of verse text. ... many more verses ...
I think this happens because the "publisher" who put in the section divisions doesn't fully agree with the versification they are using. Together in His Service, DM > > > Troy > > > >>> Anyway, just wanted to technical state the difference between the two mechanisms. >>> >>> Troy >>> >>> >>> >>> >>> >>> On 01/21/2013 03:23 PM, Peter von Kaehne wrote: >>>>> Von: DM Smith >>>>> In the past, I've viewed the "headings" toggle as a toggle for >>>>> non-canonical material. But the discussion on the other thread has me wondering >>>>> whether intros (non-canonical) information is handled by it. >>>>> >>>> That is exactly what I said - the headline toggle switches on everything, intros and the like. >>>> >>>> Now Troy says this is not how it should be and how the engine is handling it, but fact is that it does so. On all modules I have tried out where I know there is intro material. >>>> >>>> Now, my question - is there something very simple we module makers do wrong? Or is there some major and overarching misunderstanding between engine design, osis2mod and module makers? >>>> >>>> FWIW, usfm2osis.pl (and presumably usfm2osis.py) do not produce a verse or chapter 0 div but produce div type intro or something similar. >>>> >>>> Peter >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dmitrij.ledkov at ubuntu.com Mon Jan 21 17:49:30 2013 From: dmitrij.ledkov at ubuntu.com (Dmitrijs Ledkovs) Date: Tue, 22 Jan 2013 00:49:30 +0000 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <50FDB6A5.7040009@redhat.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358786081748-4651736.post@n4.nabble.com> <50FDB6A5.7040009@redhat.com> Message-ID: On 21 January 2013 21:44, Mat?j Cepl wrote: > On 21/01/13 18:44, Dmitrijs Ledkovs wrote: >> But when not-docked, i.e. touch screen mode. The supported SDK/UI are >> Webapps or Qt 5 / QML with specific ubuntu phone touch UI components. > > And just to add one more reasons why I believe Ubuntu Phone is DOA ... > notice Qt 5. Mark Shuttleworth was sounding in the Ubuntu Phone PR video > that these are just different UIs for the same OS. Except it is not true > ... all those Gtk applications which currently run on plain Ubuntu need > to be completely rewritten to the new framework (and yes, those new apps > could run both on desktop and phone, but complete rewrite of apps is > required). > I like Gtk+ a lot, but hardly any existing GTK apps are touch friendly. So they need to be overhauled anyway. Re factoring & rewriting is usually quicker. iPhone is Objective-C, while android is approx. java based. Yet, many popular applications are available on both with near matching features (i recently switched from iphone to android so had a fresh switch-over comparison). I'm not competent enough to judge similarities & differences between Objective-C (only have grass-root NSObject knoweledge) / Java (nil) / Qt (nil). And how wide spread Qt is. W.r.t. DOA well... time will tell =) Regards, Dmitrijs. From mcepl at redhat.com Tue Jan 22 04:15:52 2013 From: mcepl at redhat.com (=?UTF-8?B?TWF0xJtqIENlcGw=?=) Date: Tue, 22 Jan 2013 12:15:52 +0100 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: References: <1358107307823-4651673.post@n4.nabble.com> <1358786081748-4651736.post@n4.nabble.com> <50FDB6A5.7040009@redhat.com> Message-ID: <50FE74E8.7080703@redhat.com> On 22/01/13 01:49, Dmitrijs Ledkovs wrote: > W.r.t. DOA well... time will tell =) I said "I belive" ... we'll see. Mat?j From thulester at gmail.com Tue Jan 22 11:09:12 2013 From: thulester at gmail.com (Andrew Thule) Date: Tue, 22 Jan 2013 13:09:12 -0500 Subject: [sword-devel] Method Name Normalization In-Reply-To: <50FD2B62.8000009@crosswire.org> References: <50FAC626.3000304@crosswire.org> <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> <50FD2B62.8000009@crosswire.org> Message-ID: I just grabbed a fresh copy of sword via svn. On Sat, Jan 19, 2013 at 11:13 AM, Troy A. Griffitts wrote: In anticipation of a new release, I have a large checkin I'm about to commit which will break everything for everyone compiling with -Werror. The Makefile that comes with sword uses the -Werror directive, so grabbing via svn and making is currently broken on the making of .libs/swmodule.o. Could it be fixed it so that what comes via svn isn't broken. Is the solution to remove -Werror and try again? ~A On Mon, Jan 21, 2013 at 6:49 AM, Troy A. Griffitts wrote: > On 01/21/2013 12:28 PM, Nic Carter wrote: > >> Is there a reason for this being the abbreviation and not >> "setIntroductions(bool)" and "isIntroductions()"? I find it strange that >> you've fixed up "Lang()" and introduced "Intros()"... But, thanks for this >> change. It was confusing before! :) >> > > Yeah, well. :) Here was my thinking on this. No one says "Lang" as a > spoken abbreviation for Language, but we all use "Intros" regularly. In > fact-- seeking to justify my behavior-- it looks like google even claims > "intro" as it's own word: https://www.google.com/search?** > q=definition+intro > > > :) > > > Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) I >> say "think" cause it threw an error for me and then I realised I didn't >> need that in my stuff, so I simply deleted it rather than "fix" it.. >> > > Fixed. Thanks for the heads up Nic. > > Troy > > > . ;) Thanks for all of this. :) Still double checking it all with my >> stuff, but looking good so far :) Thanks, ybic nic... :) >> ______________________________**_________________ sword-devel mailing >> list: sword-devel at crosswire.org http://www.crosswire.org/** >> mailman/listinfo/sword-develInstructions to unsubscribe/change your settings at above page >> > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Tue Jan 22 11:16:14 2013 From: thulester at gmail.com (Andrew Thule) Date: Tue, 22 Jan 2013 13:16:14 -0500 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> <50FD2B62.8000009@crosswire.org> Message-ID: To add .. the cmake build works, it is only the traditional ./configure;make;make install that appears broken. ~A On Tue, Jan 22, 2013 at 1:09 PM, Andrew Thule wrote: > I just grabbed a fresh copy of sword via svn. > > > On Sat, Jan 19, 2013 at 11:13 AM, Troy A. Griffitts wrote: > In anticipation of a new release, I have a large checkin I'm about to > commit which will break everything for everyone compiling with -Werror. > > The Makefile that comes with sword uses the -Werror directive, so grabbing > via svn and making is currently broken on the making of .libs/swmodule.o. > > Could it be fixed it so that what comes via svn isn't broken. Is the > solution to remove -Werror and try again? > > ~A > > > On Mon, Jan 21, 2013 at 6:49 AM, Troy A. Griffitts wrote: > >> On 01/21/2013 12:28 PM, Nic Carter wrote: >> >>> Is there a reason for this being the abbreviation and not >>> "setIntroductions(bool)" and "isIntroductions()"? I find it strange that >>> you've fixed up "Lang()" and introduced "Intros()"... But, thanks for this >>> change. It was confusing before! :) >>> >> >> Yeah, well. :) Here was my thinking on this. No one says "Lang" as a >> spoken abbreviation for Language, but we all use "Intros" regularly. In >> fact-- seeking to justify my behavior-- it looks like google even claims >> "intro" as it's own word: https://www.google.com/search?** >> q=definition+intro >> >> >> :) >> >> >> Also, I think you forgot a "const" in echomod.cpp? (one of the tests.) I >>> say "think" cause it threw an error for me and then I realised I didn't >>> need that in my stuff, so I simply deleted it rather than "fix" it.. >>> >> >> Fixed. Thanks for the heads up Nic. >> >> Troy >> >> >> . ;) Thanks for all of this. :) Still double checking it all with my >>> stuff, but looking good so far :) Thanks, ybic nic... :) >>> ______________________________**_________________ sword-devel mailing >>> list: sword-devel at crosswire.org http://www.crosswire.org/** >>> mailman/listinfo/sword-develInstructions to unsubscribe/change your settings at above page >>> >> >> >> ______________________________**_________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/**mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Tue Jan 22 11:23:43 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Tue, 22 Jan 2013 12:23:43 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> <2CFC35C2-3BB8-4E07-90B7-46F34F9A2E99@mac.com> <50FD2B62.8000009@crosswire.org> Message-ID: On Tue, Jan 22, 2013 at 12:16 PM, Andrew Thule wrote: > To add .. the cmake build works, it is only the traditional > ./configure;make;make install that appears broken. > If you run the cmake toolchain with "make VERBOSE=1" do the commands have -Werror -Wall enabled? If not, try running cmake with the flag SWORD_ENABLE_WARNINGS set to "Yes" and build again. And please be more specific when you say "appears broken". Plenty of us have built with this commit without it being broken, so we need more information about what you mean. --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Tue Jan 22 12:17:23 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Tue, 22 Jan 2013 19:17:23 +0000 Subject: [sword-devel] Localising STEP Message-ID: Hi I'm looking for volunteers who would be willing to help localise STEP. We're aiming for 97 languages, so if you speak a language other than English and have a few spare hours, please let me know. We're currently looking at around 200 phrases of 1-2 words each. We'd like to get 2 translators per language (one to translate, one to proof read). We're using Crowdin to manage our translations: http://crowdin.net/project/step so please do register if you're interested. If your language is not listed, please let me know and we will include it! I can send you a link to our Beta release of STEP offline. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Tue Jan 22 21:45:03 2013 From: thulester at gmail.com (Andrew Thule) Date: Tue, 22 Jan 2013 23:45:03 -0500 Subject: [sword-devel] SFTP Support In-Reply-To: References: <50D7DC71.1040002@crosswire.org> Message-ID: Some versions of Ubuntu don't come with SFTP support included in CURL (because of --without-libssh2 being set). If this is the case, instructions to ensure SFTP is available in curl and libcurl can be found here: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029 ~A On Fri, Dec 28, 2012 at 1:42 PM, Greg Hellings wrote: > Further digging with help from our friends has revealed this nugget: > > $ curl-config --protocols > > produces a newline-delimited list of protocols that the particular > build of libcurl supports. curl-config is a shell script which can be > run on the build system and should satisfy both the requirements of > native builds and cross-compiling support. We could use this to set a > compiler macro indicating support (or not) for SFTP in the target > libcurl library. > > If someone wants to tackle that in the autotools world, I can add > detection to CMake as well. A simple command such as > $ curl-config --protocols | grep SFTP | wc -l > 1 > > in Fedora will result in a value of 1 or greater if SFTP is supported > while it should produce 0 if SFTP support is left out. An Ubuntu > system produce this output: > $ curl-config --protocols | grep SFTP | wc -l > 0 > > And it even works for cross-compiling: > $ /usr/i686-w64-mingw32/sys-root/mingw/bin/curl-config --protocols | > grep SFTP | wc -l > 1 > > > This appears to be our best way forward if we want to enable > compile-time enabling or disabling of this option. > > --Greg > > On Mon, Dec 24, 2012 at 8:43 AM, Greg Hellings > wrote: > > Troy, > > > > On Sun, Dec 23, 2012 at 10:39 PM, Troy A. Griffitts > > wrote: > >> Dear Greg, > >> > >> Looking to apply this SFTP patch, could you give me some background as > to > >> why the check to ignore across all transports for '.' and '..'? > > > > Our downloading method runs recursively from the given directory until > > it runs out of directory depth. FTP servers don't usually seem to > > return . and .. as valid paths, and the HTTP(S) transport attempts to > > parse the returned HTML page to avoid the link to the parent > > directory. But whatever options are passed by cURL to the SFTP > > transport resulted in it returning . and .. as paths within the > > current directory. Because '.' came first in the list, the installmgr > > was running through an infinite loop whenever it tried to pull data > > from the server. > > > > I added it at the level of all transports because we don't want to > > either loop infinitely on '.' or accidentally pull a whole server > > recursively by following '..' to the root of the server. It might be a > > server config option that permits it, but I wanted to avoid the > > possibility of the InlstallMgr class getting choked up on it. > > > > --Greg > > > >> > >> Thanks, > >> > >> Troy > >> > >> > >> > >> > >> On 12/03/2012 04:06 PM, Greg Hellings wrote: > >> > >> The attached patch will introduce support for SFTPSource transports in > >> the SWORD engine, allowing a user to access remote repositories over > >> SFTP (which is enabled by default when a user enables SSH). > >> > >> --Greg > >> > >> > >> > >> _______________________________________________ > >> sword-devel mailing list: sword-devel at crosswire.org > >> http://www.crosswire.org/mailman/listinfo/sword-devel > >> Instructions to unsubscribe/change your settings at above page > >> > >> > >> > >> _______________________________________________ > >> sword-devel mailing list: sword-devel at crosswire.org > >> http://www.crosswire.org/mailman/listinfo/sword-devel > >> Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trampster at gmail.com Tue Jan 22 23:12:07 2013 From: trampster at gmail.com (Daniel Hughes) Date: Wed, 23 Jan 2013 19:12:07 +1300 Subject: [sword-devel] Location of prebuilt lucene indexes. Message-ID: I noticed that some of the front ends offer the option of downloading prebuilt lucene indexes. However I can't seem to find them on ftp://ftp.crosswire.org Where are they hosted? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbarnesweb at yahoo.com Wed Jan 23 06:38:45 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Wed, 23 Jan 2013 05:38:45 -0800 (PST) Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> Message-ID: <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> Did a fresh checkout of?https://crosswire.org/svn/sword/trunk. Changed to bindings/objc. 1) The bindings/objc/README instructions are inaccurate. There is no Makefile in build_sword. 2) The build breaks in build_sword/build_mac_sword.sh. $ cd build_clucene $ make release-fat ... looks like successful build for 3 platforms $ cd ../build_sword $?./build_mac_sword.sh -a fat -c ... ./configure: line 15671: syntax error near unexpected token `CLUCENE2,' ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 2.3,,true)' $?pkg-config --cflags --libs libclucene-core -I/usr/local/include -I/usr/local/include/CLucene/ext ?-L/usr/local/lib/ -lclucene-core $?which pkg-config /usr/bin/pkg-config ??System Version:Mac OS X 10.6.8 (10K549) ... ??Model Name:MacBook Pro ? Model Identifier:MacBookPro6,2 ? Processor Name:Intel Core i5 ? Any help appreciated. Jeff From greg.hellings at gmail.com Wed Jan 23 06:49:17 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Wed, 23 Jan 2013 07:49:17 -0600 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> Message-ID: The Obj-C bindings have not been updated since Troy's major commit to deprecate methods and the like. However, the error you're seeing appears to be a result of missing some of the autofoo material that you need. Do you have any information on the state of your autotools package? That might help the Obj-C maintainer with your problem. --Greg On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes wrote: > Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to > bindings/objc. > > 1) The bindings/objc/README instructions are inaccurate. There is no > Makefile in build_sword. > 2) The build breaks in build_sword/build_mac_sword.sh. > > $ cd build_clucene > > $ make release-fat > ... > looks like successful build for 3 platforms > > $ cd ../build_sword > $ ./build_mac_sword.sh -a fat -c > > ... > > ./configure: line 15671: syntax error near unexpected token `CLUCENE2,' > ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= > 2.3,,true)' > > $ pkg-config --cflags --libs libclucene-core > -I/usr/local/include -I/usr/local/include/CLucene/ext -L/usr/local/lib/ > -lclucene-core > > $ which pkg-config > /usr/bin/pkg-config > > System Version:Mac OS X 10.6.8 (10K549) > ... > Model Name:MacBook Pro > Model Identifier:MacBookPro6,2 > Processor Name:Intel Core i5 > > Any help appreciated. > > Jeff > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbarnesweb at yahoo.com Wed Jan 23 07:31:18 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Wed, 23 Jan 2013 06:31:18 -0800 (PST) Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> Message-ID: <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> Thanks for the quick response, Greg. PACCPL-334LAGYA:trunk jbarne200$ which autoconf /usr/bin/autoconf PACCPL-334LAGYA:trunk jbarne200$ which automake /usr/bin/automake PACCPL-334LAGYA:trunk jbarne200$ which libtool /usr/bin/libtool PACCPL-334LAGYA:trunk jbarne200$ which aclocal /usr/bin/aclocal PACCPL-334LAGYA:trunk jbarne200$ which autoheader /usr/bin/autoheader I was originally missing pkg-config. I installed it (for some reason the mac flavor is installed in /opt) and created a symbolic link to it in /usr/bin. I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I was able to build using trunk/autogen.sh. Still not able to build using?bindings/objc/build_sword/build_mac_sword.sh. I get the error mentioned in my original post. It might help mac users to have an environment check script (I still don't have a full command of gnu on mac). Something like the following might be useful. #!/bin/sh echo "Checking build environment" autoconf --help >/dev/null || exit $? automake --help >/dev/null || exit $? ... etc Jeff >________________________________ > From: Greg Hellings >To: Jeff Barnes ; SWORD Developers' Collaboration Forum >Sent: Wednesday, January 23, 2013 8:49 AM >Subject: Re: [sword-devel] bindings/objc build broken > > >The Obj-C bindings have not been updated since Troy's major commit to deprecate methods and the like. However, the error you're seeing appears to be a result of missing some of the autofoo material that you need. Do you have any information on the state of your autotools package? That might help the Obj-C maintainer with your problem. > > >--Greg > > > >On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes wrote: > >Did a fresh checkout of?https://crosswire.org/svn/sword/trunk. Changed to bindings/objc. >> >>1) The bindings/objc/README instructions are inaccurate. There is no Makefile in build_sword. >>2) The build breaks in build_sword/build_mac_sword.sh. >> >>$ cd build_clucene >> >>$ make release-fat >>... >>looks like successful build for 3 platforms >> >>$ cd ../build_sword >>$?./build_mac_sword.sh -a fat -c >> >>... >> >>./configure: line 15671: syntax error near unexpected token `CLUCENE2,' >>./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 2.3,,true)' >> >>$?pkg-config --cflags --libs libclucene-core >>-I/usr/local/include -I/usr/local/include/CLucene/ext ?-L/usr/local/lib/ -lclucene-core >> >>$?which pkg-config >>/usr/bin/pkg-config >> >>??System Version:Mac OS X 10.6.8 (10K549) >>... >>??Model Name:MacBook Pro >>? Model Identifier:MacBookPro6,2 >>? Processor Name:Intel Core i5 >>? >>Any help appreciated. >> >>Jeff >> >>_______________________________________________ >>sword-devel mailing list: sword-devel at crosswire.org >>http://www.crosswire.org/mailman/listinfo/sword-devel >>Instructions to unsubscribe/change your settings at above page >> > > > From manfred.bergmann at me.com Wed Jan 23 07:45:41 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 15:45:41 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> Message-ID: <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> Hi. The build scripts are deprecated and should be removed altogether. Try building using the ObjCSword Xcode project. I just made some code changes lately so it should still work. Manfred Am 23.01.2013 um 15:31 schrieb Jeff Barnes : > Thanks for the quick response, Greg. > > PACCPL-334LAGYA:trunk jbarne200$ which autoconf > /usr/bin/autoconf > PACCPL-334LAGYA:trunk jbarne200$ which automake > /usr/bin/automake > PACCPL-334LAGYA:trunk jbarne200$ which libtool > /usr/bin/libtool > PACCPL-334LAGYA:trunk jbarne200$ which aclocal > /usr/bin/aclocal > PACCPL-334LAGYA:trunk jbarne200$ which autoheader > /usr/bin/autoheader > > I was originally missing pkg-config. I installed it (for some reason the mac flavor is installed in /opt) and created a symbolic link to it in /usr/bin. I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I was able to build using trunk/autogen.sh. > > Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. I get the error mentioned in my original post. > > It might help mac users to have an environment check script (I still don't have a full command of gnu on mac). Something like the following might be useful. > > #!/bin/sh > echo "Checking build environment" > autoconf --help >/dev/null || exit $? > automake --help >/dev/null || exit $? > ... > etc > > Jeff > > >> ________________________________ >> From: Greg Hellings >> To: Jeff Barnes ; SWORD Developers' Collaboration Forum >> Sent: Wednesday, January 23, 2013 8:49 AM >> Subject: Re: [sword-devel] bindings/objc build broken >> >> >> The Obj-C bindings have not been updated since Troy's major commit to deprecate methods and the like. However, the error you're seeing appears to be a result of missing some of the autofoo material that you need. Do you have any information on the state of your autotools package? That might help the Obj-C maintainer with your problem. >> >> >> --Greg >> >> >> >> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes wrote: >> >> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to bindings/objc. >>> >>> 1) The bindings/objc/README instructions are inaccurate. There is no Makefile in build_sword. >>> 2) The build breaks in build_sword/build_mac_sword.sh. >>> >>> $ cd build_clucene >>> >>> $ make release-fat >>> ... >>> looks like successful build for 3 platforms >>> >>> $ cd ../build_sword >>> $ ./build_mac_sword.sh -a fat -c >>> >>> ... >>> >>> ./configure: line 15671: syntax error near unexpected token `CLUCENE2,' >>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 2.3,,true)' >>> >>> $ pkg-config --cflags --libs libclucene-core >>> -I/usr/local/include -I/usr/local/include/CLucene/ext -L/usr/local/lib/ -lclucene-core >>> >>> $ which pkg-config >>> /usr/bin/pkg-config >>> >>> System Version:Mac OS X 10.6.8 (10K549) >>> ... >>> Model Name:MacBook Pro >>> Model Identifier:MacBookPro6,2 >>> Processor Name:Intel Core i5 >>> >>> Any help appreciated. >>> >>> Jeff >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> >> > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From manfred.bergmann at me.com Wed Jan 23 07:51:58 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 15:51:58 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> Message-ID: If you want to build from command line you can also use something like this: # xcodebuild -target "" -configuration "" clean build The pre-lion Xcode project may also be outdated as I didn't have the time to maintain it. Manfred Am 23.01.2013 um 15:45 schrieb Manfred Bergmann : > Hi. > > The build scripts are deprecated and should be removed altogether. > Try building using the ObjCSword Xcode project. > I just made some code changes lately so it should still work. > > > Manfred > > Am 23.01.2013 um 15:31 schrieb Jeff Barnes : > >> Thanks for the quick response, Greg. >> >> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >> /usr/bin/autoconf >> PACCPL-334LAGYA:trunk jbarne200$ which automake >> /usr/bin/automake >> PACCPL-334LAGYA:trunk jbarne200$ which libtool >> /usr/bin/libtool >> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >> /usr/bin/aclocal >> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >> /usr/bin/autoheader >> >> I was originally missing pkg-config. I installed it (for some reason the mac flavor is installed in /opt) and created a symbolic link to it in /usr/bin. I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I was able to build using trunk/autogen.sh. >> >> Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. I get the error mentioned in my original post. >> >> It might help mac users to have an environment check script (I still don't have a full command of gnu on mac). Something like the following might be useful. >> >> #!/bin/sh >> echo "Checking build environment" >> autoconf --help >/dev/null || exit $? >> automake --help >/dev/null || exit $? >> ... >> etc >> >> Jeff >> >> >>> ________________________________ >>> From: Greg Hellings >>> To: Jeff Barnes ; SWORD Developers' Collaboration Forum >>> Sent: Wednesday, January 23, 2013 8:49 AM >>> Subject: Re: [sword-devel] bindings/objc build broken >>> >>> >>> The Obj-C bindings have not been updated since Troy's major commit to deprecate methods and the like. However, the error you're seeing appears to be a result of missing some of the autofoo material that you need. Do you have any information on the state of your autotools package? That might help the Obj-C maintainer with your problem. >>> >>> >>> --Greg >>> >>> >>> >>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes wrote: >>> >>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed to bindings/objc. >>>> >>>> 1) The bindings/objc/README instructions are inaccurate. There is no Makefile in build_sword. >>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>> >>>> $ cd build_clucene >>>> >>>> $ make release-fat >>>> ... >>>> looks like successful build for 3 platforms >>>> >>>> $ cd ../build_sword >>>> $ ./build_mac_sword.sh -a fat -c >>>> >>>> ... >>>> >>>> ./configure: line 15671: syntax error near unexpected token `CLUCENE2,' >>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 2.3,,true)' >>>> >>>> $ pkg-config --cflags --libs libclucene-core >>>> -I/usr/local/include -I/usr/local/include/CLucene/ext -L/usr/local/lib/ -lclucene-core >>>> >>>> $ which pkg-config >>>> /usr/bin/pkg-config >>>> >>>> System Version:Mac OS X 10.6.8 (10K549) >>>> ... >>>> Model Name:MacBook Pro >>>> Model Identifier:MacBookPro6,2 >>>> Processor Name:Intel Core i5 >>>> >>>> Any help appreciated. >>>> >>>> Jeff >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From jbarnesweb at yahoo.com Wed Jan 23 08:09:48 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Wed, 23 Jan 2013 07:09:48 -0800 (PST) Subject: [sword-devel] bindings/objc build broken In-Reply-To: <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> Message-ID: <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> I opened ObjCSword.xcodeproj and tried building. It failed with the following build log. Build sword of project ObjCSword with configuration Debug Check dependencies [BEROR]error: There is no SDK with the name or path 'macosx10.7' Requires Mountain Lion to build? I'm on Lion. I tried ObjCSword_preLion.xcodeproj, too. It failed with the following in the build log. Build ObjCSword of project ObjCSword_preLion with configuration Debug SymLink build/Debug/ObjCSword.framework/Versions/Current A cd /Users/jbarne200/sword/trunk/bindings/objc /bin/ln -sf A /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/Current SymLink build/Debug/ObjCSword.framework/Resources Versions/Current/Resources cd /Users/jbarne200/sword/trunk/bindings/objc /bin/ln -sf Versions/Current/Resources /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Resources SymLink build/Debug/ObjCSword.framework/ObjCSword Versions/Current/ObjCSword cd /Users/jbarne200/sword/trunk/bindings/objc /bin/ln -sf Versions/Current/ObjCSword /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/ObjCSword SymLink build/Debug/ObjCSword.framework/Headers Versions/Current/Headers cd /Users/jbarne200/sword/trunk/bindings/objc /bin/ln -sf Versions/Current/Headers /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Headers ProcessInfoPlistFile build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist Info.plist cd /Users/jbarne200/sword/trunk/bindings/objc builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx -o /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/ObjCSword.h ObjCSword.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBible.h src/SwordBible.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleBook.h src/SwordBibleBook.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleChapter.h src/SwordBibleChapter.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleTextEntry.h src/SwordBibleTextEntry.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBook.h src/SwordBook.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordCommentary.h src/SwordCommentary.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordDictionary.h src/SwordDictionary.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSource.h src/SwordInstallSource.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSourceController.h src/SwordInstallSourceController.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers pbxcp: SwordInstallSourceController.h: No such file or directory CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordKey.h src/SwordKey.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordListKey.h src/SwordListKey.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordManager.h src/SwordManager.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule.h src/SwordModule.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTextEntry.h src/SwordModuleTextEntry.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTreeEntry.h src/SwordModuleTreeEntry.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseKey.h src/SwordVerseKey.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseManager.h src/SwordVerseManager.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/VerseEnumerator.h src/VerseEnumerator.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Notifications.h src/Notifications.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/Notifications.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Configuration.h src/services/Configuration.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/OSXConfiguration.h src/services/OSXConfiguration.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule+Index.h src/SwordModule+Index.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordLocaleManager.h src/SwordLocaleManager.h cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers CopyStringsFile build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj/InfoPlist.strings English.lproj/InfoPlist.strings cd /Users/jbarne200/sword/trunk/bindings/objc setenv ICONV /usr/bin/iconv /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings --validate --inputencoding utf-8 --outputencoding UTF-16 English.lproj/InfoPlist.strings --outdir /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings:125: warning: Insecure world writable dir /opt in PATH, mode 040777 CpResource build/Debug/ObjCSword.framework/Versions/A/Resources/locales.d ../../locales.d cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/../../locales.d /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources ProcessPCH++ /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch ObjCSword_Prefix.pch normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++-header -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch ProcessPCH /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch ObjCSword_Prefix.pch normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c-header -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o src/SwordBible.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:14: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int +[SwordBible bookIndexForSWKey:](objc_object*, _message_ref_t*, sword::VerseKey*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: 'Testament' is deprecated (declared at ../../include/versekey.h:265) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'BOOL -[SwordBible hasReference:](SwordBible*, _message_ref_t*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:186: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:189: warning: 'Chapter' is deprecated (declared at ../../include/versekey.h:287) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:190: warning: 'Verse' is deprecated (declared at ../../include/versekey.h:298) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int -[SwordBible numberOfVerseKeysForReference:](SwordBible*, _message_ref_t*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:211: warning: 'ParseVerseList' is deprecated (declared at ../../include/versekey.h:452) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:213: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int -[SwordBible chaptersForBookName:](SwordBible*, _message_ref_t*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:223: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'SwordKey* -[SwordBible createKey](SwordBible*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:389: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'long int -[SwordBible entryCount](SwordBible*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:406: warning: 'Index' is deprecated (declared at ../../include/swmodule.h:248) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:408: warning: 'Index' is deprecated (declared at ../../include/swmodule.h:248) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o src/SwordBibleBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm: In function 'objc_object* -[SwordBibleBook initWithBook:](SwordBibleBook*, _message_ref_t*, sword::VerseMgr::Book*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:40: warning: 'Testament' is deprecated (declared at ../../include/versekey.h:265) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:41: warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o src/SwordBibleChapter.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o src/SwordBibleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o src/SwordBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o src/SwordCommentary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, ?? ? ? ? ? ? ? ? from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm:14: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o src/SwordDictionary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:14: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm: In function 'void -[SwordDictionary(PrivateAPI) readKeys](SwordDictionary*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:49: warning: 'KeyText' is deprecated (declared at ../../include/swmodule.h:230) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:53: warning: 'KeyText' is deprecated (declared at ../../include/swmodule.h:230) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o src/SwordInstallSource.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o src/SwordInstallSourceController.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o i686-apple-darwin10-gcc-4.2.1: /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm: No such file or directory i686-apple-darwin10-gcc-4.2.1: warning: '-x objective-c++' after last input file has no effect i686-apple-darwin10-gcc-4.2.1: no input files Command /Developer/usr/bin/gcc-4.2 failed with exit code 1 CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o src/SwordKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'void -[SwordKey setPersist:](SwordKey*, _message_ref_t*, BOOL)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:89: warning: 'Persist' is deprecated (declared at ../../include/swkey.h:153) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'BOOL -[SwordKey persist](SwordKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:93: warning: 'Persist' is deprecated (declared at ../../include/swkey.h:146) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'int -[SwordKey error](SwordKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:97: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o src/SwordListKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:9: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'SwordListKey* -[SwordListKey initWithRef:headings:v11n:](SwordListKey*, _message_ref_t*, NSString*, BOOL, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:55: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:59: warning: 'ParseVerseList' is deprecated (declared at ../../include/versekey.h:452) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'NSInteger -[SwordListKey numberOfVerses](SwordListKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:76: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'BOOL -[SwordListKey containsKey:](SwordListKey*, _message_ref_t*, SwordVerseKey*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:97: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o src/SwordManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:14: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm: In function 'void -[SwordManager(PrivateAPI) addFiltersToModule:](SwordManager*, _message_ref_t*, SwordModule*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:64: warning: 'Markup' is deprecated (declared at ../../include/swmodule.h:345) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o src/SwordModule.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, ?? ? ? ? ? ? ? ? from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:20: /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule mainInit](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: 'SwordModule' may not respond to '-retrieveName' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: (Messages without a matching method signature /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: will be assumed to return 'id' and accept /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: '...' as arguments.) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:127: warning: 'SwordModule' may not respond to '-retrieveType' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:128: warning: 'SwordModule' may not respond to '-retrieveDescr' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:129: warning: 'SwordModule' may not respond to '-retrieveLang' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule addRenderFilter:](SwordModule*, _message_ref_t*, SwordFilter*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:185: warning: 'AddRenderFilter' is deprecated (declared at ../../include/swmodule.h:476) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule addStripFilter:](SwordModule*, _message_ref_t*, SwordFilter*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:189: warning: 'AddStripFilter' is deprecated (declared at ../../include/swmodule.h:587) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveName](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:213: warning: 'Name' is deprecated (declared at ../../include/swmodule.h:285) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:215: warning: 'Name' is deprecated (declared at ../../include/swmodule.h:285) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveDescr](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:221: warning: 'Description' is deprecated (declared at ../../include/swmodule.h:299) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:223: warning: 'Description' is deprecated (declared at ../../include/swmodule.h:299) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveLang](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:229: warning: 'Lang' is deprecated (declared at ../../include/swmodule.h:353) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:231: warning: 'Lang' is deprecated (declared at ../../include/swmodule.h:353) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveType](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:237: warning: 'Type' is deprecated (declared at ../../include/swmodule.h:313) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:239: warning: 'Type' is deprecated (declared at ../../include/swmodule.h:313) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'SwordKey* -[SwordModule createKey](SwordModule*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:508: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule setProcessEntryAttributes:](SwordModule*, _message_ref_t*, BOOL)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:563: warning: 'processEntryAttributes' is deprecated (declared at ../../include/swmodule.h:710) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o src/SwordModuleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o src/SwordModuleTreeEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o src/SwordVerseKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'SwordVerseKey* -[SwordVerseKey initWithSWVerseKey:makeCopy:](SwordVerseKey*, _message_ref_t*, sword::VerseKey*, BOOL)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:51: warning: incompatible Objective-C types assigning 'SwordKey*', expected 'SwordVerseKey*' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'SwordVerseKey* -[SwordVerseKey initWithRef:v11n:](SwordVerseKey*, _message_ref_t*, NSString*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:64: warning: incompatible Objective-C types assigning 'SwordKey*', expected 'SwordVerseKey*' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'int -[SwordVerseKey index](SwordVerseKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:92: error: 'class sword::SWKey' has no member named 'Index' /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'BOOL -[SwordVerseKey headings](SwordVerseKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:96: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'void -[SwordVerseKey setHeadings:](SwordVerseKey*, _message_ref_t*, BOOL)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:100: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'BOOL -[SwordVerseKey autoNormalize](SwordVerseKey*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:104: warning: 'AutoNormalize' is deprecated (declared at ../../include/versekey.h:380) /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'void -[SwordVerseKey setAutoNormalize:](SwordVerseKey*, _message_ref_t*, BOOL)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:108: warning: 'AutoNormalize' is deprecated (declared at ../../include/versekey.h:376) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o src/SwordVerseManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm: In function 'NSArray* -[SwordVerseManager booksForVersification:](SwordVerseManager*, _message_ref_t*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm:65: warning: comparison between signed and unsigned integer expressions CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o src/VerseEnumerator.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In function 'NSArray* -[VerseEnumerator allObjects](VerseEnumerator*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:40: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In function 'NSString* -[VerseEnumerator nextObject](VerseEnumerator*, _message_ref_t*)': /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:51: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o src/services/OSXConfiguration.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o src/services/Configuration.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o src/SwordModule+Index.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm: In function 'NSArray* -[SwordModule(Index) performIndexSearch:](SwordModule*, _message_ref_t*, NSString*)': /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm:40: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o src/SwordLocaleManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 cd /Users/jbarne200/sword/trunk/bindings/objc setenv LANG en_US.US-ASCII /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libclucene-ub.a build_clucene/build/result_inst/lib/libclucene-ub.a cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/build_clucene/build/result_inst/lib/libclucene-ub.a /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libsword-ub.a build_sword/build/result_inst/lib/libsword-ub.a cd /Users/jbarne200/sword/trunk/bindings/objc /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/build_sword/build/result_inst/lib/libsword-ub.a /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks pbxcp: libsword-ub.a: No such file or directory ----- Original Message ----- > From: Manfred Bergmann > To: Jeff Barnes ; SWORD Developers' Collaboration Forum > Cc: > Sent: Wednesday, January 23, 2013 9:45 AM > Subject: Re: [sword-devel] bindings/objc build broken > > Hi. > > The build scripts are deprecated and should be removed altogether. > Try building using the ObjCSword Xcode project. > I just made some code changes lately so it should still work. > > > Manfred > > Am 23.01.2013 um 15:31 schrieb Jeff Barnes : > >> Thanks for the quick response, Greg. >> >> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >> /usr/bin/autoconf >> PACCPL-334LAGYA:trunk jbarne200$ which automake >> /usr/bin/automake >> PACCPL-334LAGYA:trunk jbarne200$ which libtool >> /usr/bin/libtool >> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >> /usr/bin/aclocal >> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >> /usr/bin/autoheader >> >> I was originally missing pkg-config. I installed it (for some reason the > mac flavor is installed in /opt) and created a symbolic link to it in /usr/bin. > I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I > was able to build using trunk/autogen.sh. >> >> Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. > I get the error mentioned in my original post. >> >> It might help mac users to have an environment check script (I still > don't have a full command of gnu on mac). Something like the following might > be useful. >> >> #!/bin/sh >> echo "Checking build environment" >> autoconf --help >/dev/null || exit $? >> automake --help >/dev/null || exit $? >> ... >> etc >> >> Jeff >> >> >>> ________________________________ >>> From: Greg Hellings >>> To: Jeff Barnes ; SWORD Developers' > Collaboration Forum >>> Sent: Wednesday, January 23, 2013 8:49 AM >>> Subject: Re: [sword-devel] bindings/objc build broken >>> >>> >>> The Obj-C bindings have not been updated since Troy's major commit > to deprecate methods and the like. However, the error you're seeing appears > to be a result of missing some of the autofoo material that you need. Do you > have any information on the state of your autotools package? That might help the > Obj-C maintainer with your problem. >>> >>> >>> --Greg >>> >>> >>> >>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes > wrote: >>> >>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed > to bindings/objc. >>>> >>>> 1) The bindings/objc/README instructions are inaccurate. There is > no Makefile in build_sword. >>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>> >>>> $ cd build_clucene >>>> >>>> $ make release-fat >>>> ... >>>> looks like successful build for 3 platforms >>>> >>>> $ cd ../build_sword >>>> $ ./build_mac_sword.sh -a fat -c >>>> >>>> ... >>>> >>>> ./configure: line 15671: syntax error near unexpected token > `CLUCENE2,' >>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, > libclucene-core >= 2.3,,true)' >>>> >>>> $ pkg-config --cflags --libs libclucene-core >>>> -I/usr/local/include -I/usr/local/include/CLucene/ext? > -L/usr/local/lib/ -lclucene-core >>>> >>>> $ which pkg-config >>>> /usr/bin/pkg-config >>>> >>>> ? System Version:Mac OS X 10.6.8 (10K549) >>>> ... >>>> ? Model Name:MacBook Pro >>>> ? Model Identifier:MacBookPro6,2 >>>> ? Processor Name:Intel Core i5 >>>> ? >>>> Any help appreciated. >>>> >>>> Jeff >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > From dfhmch at googlemail.com Wed Jan 23 08:14:16 2013 From: dfhmch at googlemail.com (David Haslam) Date: Wed, 23 Jan 2013 07:14:16 -0800 (PST) Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: Message-ID: <1358954056263-4651763.post@n4.nabble.com> Hi Daniel, I put the question to Martin Denham (the developer of And Bible). He replied: (lightly edited by me) And Bible's indexes are here: http://www.crosswire.org/and-bible/indices/v1/ but they are only guaranteed to work with And Bible and almost definitely won't work with SWORD C++ front ends. PocketSword's indices are located separately and are incompatible. DMSmith has all the complex details on why they won't work with other apps. I based the AB downloadable indices framework on PocketSword and here are the developer's comments during our initial conversation: - clucene is version dependent, so you need to use the same version of clucene as I am. - there is a different index per module version, so if a module is updated to v1.2 from v1.1, I need to rebuild the index. - if a module doesn't have a version number, I've given it 0.0 as the version number. - the ZIP files are named "MODULE_NAME-VERSION.zip" (eg KJV-1.3.zip) - the URL is http://www.crosswire.org/pocketsword/indices/v1/ - I am planning on updating SWORD to use the latest version of clucene at some point, which is why there is currently the "v1" in the URL -- each time I update clucene in PocketSword, I will bump that number, so people using the new version of PS will have new indexes, but people still on the old version will still have the old ones available. - of course, if clucene is updated in PS, that new version of PS will have to go through and delete all the old lucene folders in each of the modules installed, as they will no longer be valid! :) David Haslam -- View this message in context: http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651763.html Sent from the SWORD Dev mailing list archive at Nabble.com. From manfred.bergmann at me.com Wed Jan 23 08:14:30 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 16:14:30 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> Message-ID: <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> If you are on Mountain Lion there may not be a 10.7 SDK. You can either install it from within Xcode or change the target SDK to 10.8. Manfred Am 23.01.2013 um 16:09 schrieb Jeff Barnes : > I opened ObjCSword.xcodeproj and tried building. It failed with the following build log. > > Build sword of project ObjCSword with configuration Debug > > Check dependencies > > [BEROR]error: There is no SDK with the name or path 'macosx10.7' > > > Requires Mountain Lion to build? I'm on Lion. > > I tried ObjCSword_preLion.xcodeproj, too. It failed with the following in the build log. > > > > > Build ObjCSword of project ObjCSword_preLion with configuration Debug > > SymLink build/Debug/ObjCSword.framework/Versions/Current A > cd /Users/jbarne200/sword/trunk/bindings/objc > /bin/ln -sf A /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/Current > > SymLink build/Debug/ObjCSword.framework/Resources Versions/Current/Resources > cd /Users/jbarne200/sword/trunk/bindings/objc > /bin/ln -sf Versions/Current/Resources /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Resources > > SymLink build/Debug/ObjCSword.framework/ObjCSword Versions/Current/ObjCSword > cd /Users/jbarne200/sword/trunk/bindings/objc > /bin/ln -sf Versions/Current/ObjCSword /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/ObjCSword > > SymLink build/Debug/ObjCSword.framework/Headers Versions/Current/Headers > cd /Users/jbarne200/sword/trunk/bindings/objc > /bin/ln -sf Versions/Current/Headers /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Headers > > ProcessInfoPlistFile build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist Info.plist > cd /Users/jbarne200/sword/trunk/bindings/objc > builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx -o /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/ObjCSword.h ObjCSword.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBible.h src/SwordBible.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleBook.h src/SwordBibleBook.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleChapter.h src/SwordBibleChapter.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleTextEntry.h src/SwordBibleTextEntry.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBook.h src/SwordBook.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordCommentary.h src/SwordCommentary.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordDictionary.h src/SwordDictionary.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSource.h src/SwordInstallSource.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSourceController.h src/SwordInstallSourceController.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > pbxcp: SwordInstallSourceController.h: No such file or directory > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordKey.h src/SwordKey.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordListKey.h src/SwordListKey.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordManager.h src/SwordManager.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule.h src/SwordModule.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTextEntry.h src/SwordModuleTextEntry.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTreeEntry.h src/SwordModuleTreeEntry.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseKey.h src/SwordVerseKey.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseManager.h src/SwordVerseManager.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/VerseEnumerator.h src/VerseEnumerator.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Notifications.h src/Notifications.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/Notifications.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Configuration.h src/services/Configuration.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/OSXConfiguration.h src/services/OSXConfiguration.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule+Index.h src/SwordModule+Index.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordLocaleManager.h src/SwordLocaleManager.h > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.h /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers > > CopyStringsFile build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj/InfoPlist.strings English.lproj/InfoPlist.strings > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv ICONV /usr/bin/iconv > /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings --validate --inputencoding utf-8 --outputencoding UTF-16 English.lproj/InfoPlist.strings --outdir /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj > > /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings:125: warning: Insecure world writable dir /opt in PATH, mode 040777 > > CpResource build/Debug/ObjCSword.framework/Versions/A/Resources/locales.d ../../locales.d > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/../../locales.d /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources > > ProcessPCH++ /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch ObjCSword_Prefix.pch normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++-header -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch > > ProcessPCH /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch ObjCSword_Prefix.pch normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c-header -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o src/SwordBible.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:14: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int +[SwordBible bookIndexForSWKey:](objc_object*, _message_ref_t*, sword::VerseKey*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: 'Testament' is deprecated (declared at ../../include/versekey.h:265) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'BOOL -[SwordBible hasReference:](SwordBible*, _message_ref_t*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:186: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:189: warning: 'Chapter' is deprecated (declared at ../../include/versekey.h:287) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:190: warning: 'Verse' is deprecated (declared at ../../include/versekey.h:298) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int -[SwordBible numberOfVerseKeysForReference:](SwordBible*, _message_ref_t*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:211: warning: 'ParseVerseList' is deprecated (declared at ../../include/versekey.h:452) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:213: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'int -[SwordBible chaptersForBookName:](SwordBible*, _message_ref_t*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:223: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'SwordKey* -[SwordBible createKey](SwordBible*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:389: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function 'long int -[SwordBible entryCount](SwordBible*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:406: warning: 'Index' is deprecated (declared at ../../include/swmodule.h:248) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:408: warning: 'Index' is deprecated (declared at ../../include/swmodule.h:248) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o src/SwordBibleBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm: In function 'objc_object* -[SwordBibleBook initWithBook:](SwordBibleBook*, _message_ref_t*, sword::VerseMgr::Book*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:40: warning: 'Testament' is deprecated (declared at ../../include/versekey.h:265) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:41: warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o src/SwordBibleChapter.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o src/SwordBibleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o src/SwordBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o src/SwordCommentary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, > from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm:14: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o src/SwordDictionary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:14: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm: In function 'void -[SwordDictionary(PrivateAPI) readKeys](SwordDictionary*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:49: warning: 'KeyText' is deprecated (declared at ../../include/swmodule.h:230) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:53: warning: 'KeyText' is deprecated (declared at ../../include/swmodule.h:230) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o src/SwordInstallSource.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o src/SwordInstallSourceController.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o > > i686-apple-darwin10-gcc-4.2.1: /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm: No such file or directory > i686-apple-darwin10-gcc-4.2.1: warning: '-x objective-c++' after last input file has no effect > i686-apple-darwin10-gcc-4.2.1: no input files > Command /Developer/usr/bin/gcc-4.2 failed with exit code 1 > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o src/SwordKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'void -[SwordKey setPersist:](SwordKey*, _message_ref_t*, BOOL)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:89: warning: 'Persist' is deprecated (declared at ../../include/swkey.h:153) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'BOOL -[SwordKey persist](SwordKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:93: warning: 'Persist' is deprecated (declared at ../../include/swkey.h:146) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function 'int -[SwordKey error](SwordKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:97: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o src/SwordListKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:9: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'SwordListKey* -[SwordListKey initWithRef:headings:v11n:](SwordListKey*, _message_ref_t*, NSString*, BOOL, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:55: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:59: warning: 'ParseVerseList' is deprecated (declared at ../../include/versekey.h:452) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'NSInteger -[SwordListKey numberOfVerses](SwordListKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:76: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function 'BOOL -[SwordListKey containsKey:](SwordListKey*, _message_ref_t*, SwordVerseKey*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:97: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o src/SwordManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:14: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm: In function 'void -[SwordManager(PrivateAPI) addFiltersToModule:](SwordManager*, _message_ref_t*, SwordModule*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:64: warning: 'Markup' is deprecated (declared at ../../include/swmodule.h:345) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o src/SwordModule.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o > > In file included from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, > from /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:20: > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: ObjCSword/SwordInstallSourceManager.h: No such file or directory > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule mainInit](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: 'SwordModule' may not respond to '-retrieveName' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: (Messages without a matching method signature > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: will be assumed to return 'id' and accept > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: '...' as arguments.) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:127: warning: 'SwordModule' may not respond to '-retrieveType' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:128: warning: 'SwordModule' may not respond to '-retrieveDescr' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:129: warning: 'SwordModule' may not respond to '-retrieveLang' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule addRenderFilter:](SwordModule*, _message_ref_t*, SwordFilter*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:185: warning: 'AddRenderFilter' is deprecated (declared at ../../include/swmodule.h:476) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule addStripFilter:](SwordModule*, _message_ref_t*, SwordFilter*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:189: warning: 'AddStripFilter' is deprecated (declared at ../../include/swmodule.h:587) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveName](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:213: warning: 'Name' is deprecated (declared at ../../include/swmodule.h:285) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:215: warning: 'Name' is deprecated (declared at ../../include/swmodule.h:285) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveDescr](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:221: warning: 'Description' is deprecated (declared at ../../include/swmodule.h:299) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:223: warning: 'Description' is deprecated (declared at ../../include/swmodule.h:299) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveLang](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:229: warning: 'Lang' is deprecated (declared at ../../include/swmodule.h:353) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:231: warning: 'Lang' is deprecated (declared at ../../include/swmodule.h:353) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'NSString* -[SwordModule retrieveType](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:237: warning: 'Type' is deprecated (declared at ../../include/swmodule.h:313) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:239: warning: 'Type' is deprecated (declared at ../../include/swmodule.h:313) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'SwordKey* -[SwordModule createKey](SwordModule*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:508: warning: 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function 'void -[SwordModule setProcessEntryAttributes:](SwordModule*, _message_ref_t*, BOOL)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:563: warning: 'processEntryAttributes' is deprecated (declared at ../../include/swmodule.h:710) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o src/SwordModuleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o src/SwordModuleTreeEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o src/SwordVerseKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'SwordVerseKey* -[SwordVerseKey initWithSWVerseKey:makeCopy:](SwordVerseKey*, _message_ref_t*, sword::VerseKey*, BOOL)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:51: warning: incompatible Objective-C types assigning 'SwordKey*', expected 'SwordVerseKey*' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'SwordVerseKey* -[SwordVerseKey initWithRef:v11n:](SwordVerseKey*, _message_ref_t*, NSString*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:64: warning: incompatible Objective-C types assigning 'SwordKey*', expected 'SwordVerseKey*' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'int -[SwordVerseKey index](SwordVerseKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:92: error: 'class sword::SWKey' has no member named 'Index' > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'BOOL -[SwordVerseKey headings](SwordVerseKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:96: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'void -[SwordVerseKey setHeadings:](SwordVerseKey*, _message_ref_t*, BOOL)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:100: warning: 'Headings' is deprecated (declared at ../../include/versekey.h:392) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'BOOL -[SwordVerseKey autoNormalize](SwordVerseKey*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:104: warning: 'AutoNormalize' is deprecated (declared at ../../include/versekey.h:380) > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In function 'void -[SwordVerseKey setAutoNormalize:](SwordVerseKey*, _message_ref_t*, BOOL)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:108: warning: 'AutoNormalize' is deprecated (declared at ../../include/versekey.h:376) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o src/SwordVerseManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm: In function 'NSArray* -[SwordVerseManager booksForVersification:](SwordVerseManager*, _message_ref_t*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm:65: warning: comparison between signed and unsigned integer expressions > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o src/VerseEnumerator.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In function 'NSArray* -[VerseEnumerator allObjects](VerseEnumerator*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:40: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In function 'NSString* -[VerseEnumerator nextObject](VerseEnumerator*, _message_ref_t*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:51: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o src/services/OSXConfiguration.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o src/services/Configuration.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include > -I../../include -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.m -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o src/SwordModule+Index.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o > > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm: In function 'NSArray* -[SwordModule(Index) performIndexSearch:](SwordModule*, _message_ref_t*, NSString*)': > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm:40: warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) > > CompileC build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o src/SwordLocaleManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 > cd /Users/jbarne200/sword/trunk/bindings/objc > setenv LANG en_US.US-ASCII > /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap -iquote /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug -F/Developer/Library/Frameworks -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include > -I../../include/internal -I../../include/internal/regex -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources -DDEBUG -include /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.mm -o /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o > > PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libclucene-ub.a build_clucene/build/result_inst/lib/libclucene-ub.a > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/build_clucene/build/result_inst/lib/libclucene-ub.a /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks > > PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libsword-ub.a build_sword/build/result_inst/lib/libsword-ub.a > cd /Users/jbarne200/sword/trunk/bindings/objc > /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks /Users/jbarne200/sword/trunk/bindings/objc/build_sword/build/result_inst/lib/libsword-ub.a /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks > > pbxcp: libsword-ub.a: No such file or directory > > > > ----- Original Message ----- >> From: Manfred Bergmann >> To: Jeff Barnes ; SWORD Developers' Collaboration Forum >> Cc: >> Sent: Wednesday, January 23, 2013 9:45 AM >> Subject: Re: [sword-devel] bindings/objc build broken >> >> Hi. >> >> The build scripts are deprecated and should be removed altogether. >> Try building using the ObjCSword Xcode project. >> I just made some code changes lately so it should still work. >> >> >> Manfred >> >> Am 23.01.2013 um 15:31 schrieb Jeff Barnes : >> >>> Thanks for the quick response, Greg. >>> >>> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >>> /usr/bin/autoconf >>> PACCPL-334LAGYA:trunk jbarne200$ which automake >>> /usr/bin/automake >>> PACCPL-334LAGYA:trunk jbarne200$ which libtool >>> /usr/bin/libtool >>> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >>> /usr/bin/aclocal >>> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >>> /usr/bin/autoheader >>> >>> I was originally missing pkg-config. I installed it (for some reason the >> mac flavor is installed in /opt) and created a symbolic link to it in /usr/bin. >> I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that point, I >> was able to build using trunk/autogen.sh. >>> >>> Still not able to build using bindings/objc/build_sword/build_mac_sword.sh. >> I get the error mentioned in my original post. >>> >>> It might help mac users to have an environment check script (I still >> don't have a full command of gnu on mac). Something like the following might >> be useful. >>> >>> #!/bin/sh >>> echo "Checking build environment" >>> autoconf --help >/dev/null || exit $? >>> automake --help >/dev/null || exit $? >>> ... >>> etc >>> >>> Jeff >>> >>> >>>> ________________________________ >>>> From: Greg Hellings >>>> To: Jeff Barnes ; SWORD Developers' >> Collaboration Forum >>>> Sent: Wednesday, January 23, 2013 8:49 AM >>>> Subject: Re: [sword-devel] bindings/objc build broken >>>> >>>> >>>> The Obj-C bindings have not been updated since Troy's major commit >> to deprecate methods and the like. However, the error you're seeing appears >> to be a result of missing some of the autofoo material that you need. Do you >> have any information on the state of your autotools package? That might help the >> Obj-C maintainer with your problem. >>>> >>>> >>>> --Greg >>>> >>>> >>>> >>>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes >> wrote: >>>> >>>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. Changed >> to bindings/objc. >>>>> >>>>> 1) The bindings/objc/README instructions are inaccurate. There is >> no Makefile in build_sword. >>>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>>> >>>>> $ cd build_clucene >>>>> >>>>> $ make release-fat >>>>> ... >>>>> looks like successful build for 3 platforms >>>>> >>>>> $ cd ../build_sword >>>>> $ ./build_mac_sword.sh -a fat -c >>>>> >>>>> ... >>>>> >>>>> ./configure: line 15671: syntax error near unexpected token >> `CLUCENE2,' >>>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, >> libclucene-core >= 2.3,,true)' >>>>> >>>>> $ pkg-config --cflags --libs libclucene-core >>>>> -I/usr/local/include -I/usr/local/include/CLucene/ext >> -L/usr/local/lib/ -lclucene-core >>>>> >>>>> $ which pkg-config >>>>> /usr/bin/pkg-config >>>>> >>>>> System Version:Mac OS X 10.6.8 (10K549) >>>>> ... >>>>> Model Name:MacBook Pro >>>>> Model Identifier:MacBookPro6,2 >>>>> Processor Name:Intel Core i5 >>>>> >>>>> Any help appreciated. >>>>> >>>>> Jeff >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> From jbarnesweb at yahoo.com Wed Jan 23 08:24:20 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Wed, 23 Jan 2013 07:24:20 -0800 (PST) Subject: [sword-devel] bindings/objc build broken In-Reply-To: <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> Message-ID: <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Oops. I'm not on Lion... System Software Overview: ? System Version:Mac OS X 10.6.8 (10K549) ? Kernel Version:Darwin 10.8.0 Am I out of luck? ----- Original Message ----- > From: Manfred Bergmann > To: Jeff Barnes > Cc: SWORD Developers' Collaboration Forum > Sent: Wednesday, January 23, 2013 10:14 AM > Subject: Re: [sword-devel] bindings/objc build broken > > If you are on Mountain Lion there may not be a 10.7 SDK. > You can either install it from within Xcode or change the target SDK to 10.8. > > > Manfred > > Am 23.01.2013 um 16:09 schrieb Jeff Barnes : > >> I opened ObjCSword.xcodeproj and tried building. It failed with the > following build log. >> >> Build sword of project ObjCSword with configuration Debug >> >> Check dependencies >> >> [BEROR]error: There is no SDK with the name or path 'macosx10.7' >> >> >> Requires Mountain Lion to build? I'm on Lion. >> >> I tried ObjCSword_preLion.xcodeproj, too. It failed with the following in > the build log. >> >> >> >> >> Build ObjCSword of project ObjCSword_preLion with configuration Debug >> >> SymLink build/Debug/ObjCSword.framework/Versions/Current A >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /bin/ln -sf A > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/Current >> >> SymLink build/Debug/ObjCSword.framework/Resources > Versions/Current/Resources >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /bin/ln -sf Versions/Current/Resources > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Resources >> >> SymLink build/Debug/ObjCSword.framework/ObjCSword > Versions/Current/ObjCSword >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /bin/ln -sf Versions/Current/ObjCSword > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/ObjCSword >> >> SymLink build/Debug/ObjCSword.framework/Headers Versions/Current/Headers >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /bin/ln -sf Versions/Current/Headers > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Headers >> >> ProcessInfoPlistFile > build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist Info.plist >> cd /Users/jbarne200/sword/trunk/bindings/objc >> builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx > -o > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/ObjCSword.h > ObjCSword.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBible.h > src/SwordBible.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleBook.h > src/SwordBibleBook.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleChapter.h > src/SwordBibleChapter.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleTextEntry.h > src/SwordBibleTextEntry.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBook.h > src/SwordBook.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordCommentary.h > src/SwordCommentary.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordDictionary.h > src/SwordDictionary.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSource.h > src/SwordInstallSource.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSourceController.h > src/SwordInstallSourceController.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> pbxcp: SwordInstallSourceController.h: No such file or directory >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordKey.h > src/SwordKey.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordListKey.h > src/SwordListKey.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordManager.h > src/SwordManager.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule.h > src/SwordModule.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTextEntry.h > src/SwordModuleTextEntry.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTreeEntry.h > src/SwordModuleTreeEntry.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseKey.h > src/SwordVerseKey.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseManager.h > src/SwordVerseManager.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/VerseEnumerator.h > src/VerseEnumerator.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Notifications.h > src/Notifications.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/Notifications.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Configuration.h > src/services/Configuration.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/OSXConfiguration.h > src/services/OSXConfiguration.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule+Index.h > src/SwordModule+Index.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CpHeader > build/Debug/ObjCSword.framework/Versions/A/Headers/SwordLocaleManager.h > src/SwordLocaleManager.h >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.h > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >> >> CopyStringsFile > build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj/InfoPlist.strings > English.lproj/InfoPlist.strings >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv ICONV /usr/bin/iconv >> > /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings > --validate --inputencoding utf-8 --outputencoding UTF-16 > English.lproj/InfoPlist.strings --outdir > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj >> >> > /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings:125: > warning: Insecure world writable dir /opt in PATH, mode 040777 >> >> CpResource build/Debug/ObjCSword.framework/Versions/A/Resources/locales.d > ../../locales.d >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/../../locales.d > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources >> >> ProcessPCH++ > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch > ObjCSword_Prefix.pch normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++-header -arch x86_64 > -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 > -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk > -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch >> >> ProcessPCH > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch > ObjCSword_Prefix.pch normal x86_64 objective-c com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c-header -arch x86_64 > -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks > -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk > -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o > src/SwordBible.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:14: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'int +[SwordBible bookIndexForSWKey:](objc_object*, _message_ref_t*, > sword::VerseKey*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: > 'Book' is deprecated (declared at ../../include/versekey.h:276) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: > 'Testament' is deprecated (declared at ../../include/versekey.h:265) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'BOOL -[SwordBible hasReference:](SwordBible*, _message_ref_t*, > NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:186: warning: > 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:189: warning: > 'Chapter' is deprecated (declared at ../../include/versekey.h:287) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:190: warning: > 'Verse' is deprecated (declared at ../../include/versekey.h:298) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'int -[SwordBible numberOfVerseKeysForReference:](SwordBible*, > _message_ref_t*, NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:211: warning: > 'ParseVerseList' is deprecated (declared at > ../../include/versekey.h:452) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:213: warning: > 'Error' is deprecated (declared at ../../include/swkey.h:159) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'int -[SwordBible chaptersForBookName:](SwordBible*, _message_ref_t*, > NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:223: warning: > 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'SwordKey* -[SwordBible createKey](SwordBible*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:389: warning: > 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function > 'long int -[SwordBible entryCount](SwordBible*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:406: warning: > 'Index' is deprecated (declared at ../../include/swmodule.h:248) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:408: warning: > 'Index' is deprecated (declared at ../../include/swmodule.h:248) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o > src/SwordBibleBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm: In > function 'objc_object* -[SwordBibleBook initWithBook:](SwordBibleBook*, > _message_ref_t*, sword::VerseMgr::Book*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:40: > warning: 'Testament' is deprecated (declared at > ../../include/versekey.h:265) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:41: > warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o > src/SwordBibleChapter.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o > src/SwordBibleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o > src/SwordBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o > src/SwordCommentary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >> ? ? ? ? ? ? ? ? ? from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm:14: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o > src/SwordDictionary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:14: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm: In > function 'void -[SwordDictionary(PrivateAPI) readKeys](SwordDictionary*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:49: > warning: 'KeyText' is deprecated (declared at > ../../include/swmodule.h:230) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:53: > warning: 'KeyText' is deprecated (declared at > ../../include/swmodule.h:230) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o > src/SwordInstallSource.mm normal x86_64 objective-c++ > com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o > src/SwordInstallSourceController.mm normal x86_64 objective-c++ > com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm > -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o >> >> i686-apple-darwin10-gcc-4.2.1: > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm: > No such file or directory >> i686-apple-darwin10-gcc-4.2.1: warning: '-x objective-c++' after > last input file has no effect >> i686-apple-darwin10-gcc-4.2.1: no input files >> Command /Developer/usr/bin/gcc-4.2 failed with exit code 1 >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o > src/SwordKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function > 'void -[SwordKey setPersist:](SwordKey*, _message_ref_t*, BOOL)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:89: warning: > 'Persist' is deprecated (declared at ../../include/swkey.h:153) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function > 'BOOL -[SwordKey persist](SwordKey*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:93: warning: > 'Persist' is deprecated (declared at ../../include/swkey.h:146) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function > 'int -[SwordKey error](SwordKey*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:97: warning: > 'Error' is deprecated (declared at ../../include/swkey.h:159) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o > src/SwordListKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:9: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function > 'SwordListKey* -[SwordListKey initWithRef:headings:v11n:](SwordListKey*, > _message_ref_t*, NSString*, BOOL, NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:55: warning: > 'Headings' is deprecated (declared at ../../include/versekey.h:392) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:59: warning: > 'ParseVerseList' is deprecated (declared at > ../../include/versekey.h:452) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function > 'NSInteger -[SwordListKey numberOfVerses](SwordListKey*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:76: warning: > 'Error' is deprecated (declared at ../../include/swkey.h:159) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function > 'BOOL -[SwordListKey containsKey:](SwordListKey*, _message_ref_t*, > SwordVerseKey*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:97: warning: > 'Error' is deprecated (declared at ../../include/swkey.h:159) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o > src/SwordManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:14: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm: In function > 'void -[SwordManager(PrivateAPI) addFiltersToModule:](SwordManager*, > _message_ref_t*, SwordModule*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:64: warning: > 'Markup' is deprecated (declared at ../../include/swmodule.h:345) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o > src/SwordModule.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o >> >> In file included from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >> ? ? ? ? ? ? ? ? ? from > /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:20: >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: > ObjCSword/SwordInstallSourceManager.h: No such file or directory >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'void -[SwordModule mainInit](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: > 'SwordModule' may not respond to '-retrieveName' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: > (Messages without a matching method signature >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: > will be assumed to return 'id' and accept >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: > '...' as arguments.) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:127: warning: > 'SwordModule' may not respond to '-retrieveType' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:128: warning: > 'SwordModule' may not respond to '-retrieveDescr' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:129: warning: > 'SwordModule' may not respond to '-retrieveLang' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'void -[SwordModule addRenderFilter:](SwordModule*, _message_ref_t*, > SwordFilter*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:185: warning: > 'AddRenderFilter' is deprecated (declared at > ../../include/swmodule.h:476) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'void -[SwordModule addStripFilter:](SwordModule*, _message_ref_t*, > SwordFilter*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:189: warning: > 'AddStripFilter' is deprecated (declared at > ../../include/swmodule.h:587) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'NSString* -[SwordModule retrieveName](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:213: warning: > 'Name' is deprecated (declared at ../../include/swmodule.h:285) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:215: warning: > 'Name' is deprecated (declared at ../../include/swmodule.h:285) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'NSString* -[SwordModule retrieveDescr](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:221: warning: > 'Description' is deprecated (declared at ../../include/swmodule.h:299) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:223: warning: > 'Description' is deprecated (declared at ../../include/swmodule.h:299) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'NSString* -[SwordModule retrieveLang](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:229: warning: > 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:231: warning: > 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'NSString* -[SwordModule retrieveType](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:237: warning: > 'Type' is deprecated (declared at ../../include/swmodule.h:313) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:239: warning: > 'Type' is deprecated (declared at ../../include/swmodule.h:313) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'SwordKey* -[SwordModule createKey](SwordModule*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:508: warning: > 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function > 'void -[SwordModule setProcessEntryAttributes:](SwordModule*, > _message_ref_t*, BOOL)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:563: warning: > 'processEntryAttributes' is deprecated (declared at > ../../include/swmodule.h:710) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o > src/SwordModuleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o > src/SwordModuleTreeEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o > src/SwordVerseKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'SwordVerseKey* -[SwordVerseKey > initWithSWVerseKey:makeCopy:](SwordVerseKey*, _message_ref_t*, sword::VerseKey*, > BOOL)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:51: > warning: incompatible Objective-C types assigning 'SwordKey*', expected > 'SwordVerseKey*' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'SwordVerseKey* -[SwordVerseKey initWithRef:v11n:](SwordVerseKey*, > _message_ref_t*, NSString*, NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:64: > warning: incompatible Objective-C types assigning 'SwordKey*', expected > 'SwordVerseKey*' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'int -[SwordVerseKey index](SwordVerseKey*, _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:92: error: > 'class sword::SWKey' has no member named 'Index' >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'BOOL -[SwordVerseKey headings](SwordVerseKey*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:96: > warning: 'Headings' is deprecated (declared at > ../../include/versekey.h:392) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'void -[SwordVerseKey setHeadings:](SwordVerseKey*, > _message_ref_t*, BOOL)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:100: > warning: 'Headings' is deprecated (declared at > ../../include/versekey.h:392) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'BOOL -[SwordVerseKey autoNormalize](SwordVerseKey*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:104: > warning: 'AutoNormalize' is deprecated (declared at > ../../include/versekey.h:380) >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In > function 'void -[SwordVerseKey setAutoNormalize:](SwordVerseKey*, > _message_ref_t*, BOOL)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:108: > warning: 'AutoNormalize' is deprecated (declared at > ../../include/versekey.h:376) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o > src/SwordVerseManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm: In > function 'NSArray* -[SwordVerseManager > booksForVersification:](SwordVerseManager*, _message_ref_t*, NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm:65: > warning: comparison between signed and unsigned integer expressions >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o > src/VerseEnumerator.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In > function 'NSArray* -[VerseEnumerator allObjects](VerseEnumerator*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:40: > warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In > function 'NSString* -[VerseEnumerator nextObject](VerseEnumerator*, > _message_ref_t*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:51: > warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o > src/services/OSXConfiguration.m normal x86_64 objective-c > com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o > src/services/Configuration.m normal x86_64 objective-c > com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 > -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >> -I../../include -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.m -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o > src/SwordModule+Index.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o >> >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm: In > function 'NSArray* -[SwordModule(Index) performIndexSearch:](SwordModule*, > _message_ref_t*, NSString*)': >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm:40: > warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >> >> CompileC > build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o > src/SwordLocaleManager.mm normal x86_64 objective-c++ > com.apple.compilers.gcc.4_2 >> cd /Users/jbarne200/sword/trunk/bindings/objc >> setenv LANG en_US.US-ASCII >> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 > -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type > -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only > -mmacosx-version-min=10.5 -gdwarf-2 -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap > -iquote > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap > -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug > -F/Developer/Library/Frameworks > -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >> -I../../include/internal -I../../include/internal/regex > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 > -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources > -DDEBUG -include > /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch > -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.mm -o > /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o >> >> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libclucene-ub.a > build_clucene/build/result_inst/lib/libclucene-ub.a >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/build_clucene/build/result_inst/lib/libclucene-ub.a > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >> >> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libsword-ub.a > build_sword/build/result_inst/lib/libsword-ub.a >> cd /Users/jbarne200/sword/trunk/bindings/objc >> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp > -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks > /Users/jbarne200/sword/trunk/bindings/objc/build_sword/build/result_inst/lib/libsword-ub.a > /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >> >> pbxcp: libsword-ub.a: No such file or directory >> >> >> >> ----- Original Message ----- >>> From: Manfred Bergmann >>> To: Jeff Barnes ; SWORD Developers' > Collaboration Forum >>> Cc: >>> Sent: Wednesday, January 23, 2013 9:45 AM >>> Subject: Re: [sword-devel] bindings/objc build broken >>> >>> Hi. >>> >>> The build scripts are deprecated and should be removed altogether. >>> Try building using the ObjCSword Xcode project. >>> I just made some code changes lately so it should still work. >>> >>> >>> Manfred >>> >>> Am 23.01.2013 um 15:31 schrieb Jeff Barnes > : >>> >>>> Thanks for the quick response, Greg. >>>> >>>> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >>>> /usr/bin/autoconf >>>> PACCPL-334LAGYA:trunk jbarne200$ which automake >>>> /usr/bin/automake >>>> PACCPL-334LAGYA:trunk jbarne200$ which libtool >>>> /usr/bin/libtool >>>> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >>>> /usr/bin/aclocal >>>> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >>>> /usr/bin/autoheader >>>> >>>> I was originally missing pkg-config. I installed it (for some > reason the >>> mac flavor is installed in /opt) and created a symbolic link to it in > /usr/bin. >>> I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that > point, I >>> was able to build using trunk/autogen.sh. >>>> >>>> Still not able to build using > bindings/objc/build_sword/build_mac_sword.sh. >>> I get the error mentioned in my original post. >>>> >>>> It might help mac users to have an environment check script (I > still >>> don't have a full command of gnu on mac). Something like the > following might >>> be useful. >>>> >>>> #!/bin/sh >>>> echo "Checking build environment" >>>> autoconf --help >/dev/null || exit $? >>>> automake --help >/dev/null || exit $? >>>> ... >>>> etc >>>> >>>> Jeff >>>> >>>> >>>>> ________________________________ >>>>> From: Greg Hellings >>>>> To: Jeff Barnes ; SWORD > Developers' >>> Collaboration Forum >>>>> Sent: Wednesday, January 23, 2013 8:49 AM >>>>> Subject: Re: [sword-devel] bindings/objc build broken >>>>> >>>>> >>>>> The Obj-C bindings have not been updated since Troy's major > commit >>> to deprecate methods and the like. However, the error you're seeing > appears >>> to be a result of missing some of the autofoo material that you need. > Do you >>> have any information on the state of your autotools package? That might > help the >>> Obj-C maintainer with your problem. >>>>> >>>>> >>>>> --Greg >>>>> >>>>> >>>>> >>>>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes >>> wrote: >>>>> >>>>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. > Changed >>> to bindings/objc. >>>>>> >>>>>> 1) The bindings/objc/README instructions are inaccurate. > There is >>> no Makefile in build_sword. >>>>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>>>> >>>>>> $ cd build_clucene >>>>>> >>>>>> $ make release-fat >>>>>> ... >>>>>> looks like successful build for 3 platforms >>>>>> >>>>>> $ cd ../build_sword >>>>>> $ ./build_mac_sword.sh -a fat -c >>>>>> >>>>>> ... >>>>>> >>>>>> ./configure: line 15671: syntax error near unexpected token > >>> `CLUCENE2,' >>>>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, >>> libclucene-core >= 2.3,,true)' >>>>>> >>>>>> $ pkg-config --cflags --libs libclucene-core >>>>>> -I/usr/local/include -I/usr/local/include/CLucene/ext? >>> -L/usr/local/lib/ -lclucene-core >>>>>> >>>>>> $ which pkg-config >>>>>> /usr/bin/pkg-config >>>>>> >>>>>> ? ? System Version:Mac OS X 10.6.8 (10K549) >>>>>> ... >>>>>> ? ? Model Name:MacBook Pro >>>>>> ? ? Model Identifier:MacBookPro6,2 >>>>>> ? ? Processor Name:Intel Core i5 >>>>>> ? >>>>>> Any help appreciated. >>>>>> >>>>>> Jeff >>>>>> >>>>>> _______________________________________________ >>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>> Instructions to unsubscribe/change your settings at above > page >>>>>> >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>> > From thulester at gmail.com Wed Jan 23 08:39:29 2013 From: thulester at gmail.com (Andrew Thule) Date: Wed, 23 Jan 2013 10:39:29 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: Message-ID: Daniel, the indexes themselves are created using the utility mkfastmod. If built, the lucene indexes typically sit off of the modules directory directly .. ie: .../modules/texts/ztext/kjv/lucene Administrators of a repo, you can generate the lucene directories, and have them automatically associated with the modules you are sharing by generating the index and placing it directly off the module location in your repo, ie: /pub/sword/raw/modules/texts/ztext/kjv/lucene (you can use rsync -av to copy a lucene directory from one location to another). If you look at many of the modules in the "Institute for Scripture Research" repo, those repo administrators have done this already (look at modules tbn, tkci, tkli, ttr, uzv for example). The nice thing about when repo administrators do this, is when you get a module from that repo, you also automatically get the lucene index. I do the same for my own repo. If Crosswire were to generate lucene indexes for all of the modules they host, all module downloads would automatically come with them (at least this seems to be my experience using pocketsword - only the modules that have had these directories created seem to have search index's automatic). Even so, you can generate these indexes yourself. ~A On Wed, Jan 23, 2013 at 1:12 AM, Daniel Hughes wrote: > I noticed that some of the front ends offer the option of downloading > prebuilt lucene indexes. However I can't seem to find them on > ftp://ftp.crosswire.org > > Where are they hosted? > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Wed Jan 23 09:02:31 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Wed, 23 Jan 2013 17:02:31 +0100 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: Message-ID: <20130123160231.213410@gmx.net> > Von: Andrew Thule > The nice thing about when > repo administrators do this, is when you get a module from that repo, you > also automatically get the lucene index. The reason that this is not done are manifold - including that sword and jsword indices are different, that not all platforms have the same lucene/clucene incarnation etc. Most users are better off not to use downloaded indices, but to create indices suitable for their specific frontend. Peter From refdoc at gmx.net Wed Jan 23 09:02:31 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Wed, 23 Jan 2013 17:02:31 +0100 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: Message-ID: <20130123160231.213410@gmx.net> > Von: Andrew Thule > The nice thing about when > repo administrators do this, is when you get a module from that repo, you > also automatically get the lucene index. The reason that this is not done are manifold - including that sword and jsword indices are different, that not all platforms have the same lucene/clucene incarnation etc. Most users are better off not to use downloaded indices, but to create indices suitable for their specific frontend. Peter From dmsmith at crosswire.org Wed Jan 23 09:14:27 2013 From: dmsmith at crosswire.org (DM Smith) Date: Wed, 23 Jan 2013 11:14:27 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <20130123160231.213410@gmx.net> References: <20130123160231.213410@gmx.net> Message-ID: On Jan 23, 2013, at 11:02 AM, "Peter von Kaehne" wrote: > >> Von: Andrew Thule > >> The nice thing about when >> repo administrators do this, is when you get a module from that repo, you >> also automatically get the lucene index. > > The reason that this is not done are manifold - including that sword and jsword indices are different, that not all platforms have the same lucene/clucene incarnation etc. > > Most users are better off not to use downloaded indices, but to create indices suitable for their specific frontend. To add to what Peter said, this mailing list's archives have extensive discussion on why we don't do this and why we have done it for mobile devices (only PocketSword and AndBible, and specific to them only). Also, the transfer time for a lucene index exceeds the time of a recent computer to build them, e.g. my laptop. As a Bible Desktop user, I'd really rather not transfer an index that is unusable by Bible Desktop. In Him, DM From manfred.bergmann at me.com Wed Jan 23 10:04:04 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 18:04:04 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: Well, you can play around with the build scripts. But I think they should still work. They compile the same sources as the Xcode projects would but produce a libsword.a binary which is then used in the pre-lion Xcode project. Whereas the normal (post-SL) Xcode project compiles sword lib as part of the project. If you need this for your own platform only then you don't need to build a fat binary. The fat binary compiled three times (386, i64, ppc). Also, if I look at your initial posting it looks like you need to build clucene (build_mac_clucene.sh) first because build_sword expects the library in .a format. Manfred Am 23.01.2013 um 16:24 schrieb Jeff Barnes : > Oops. I'm not on Lion... > > System Software Overview: > > System Version:Mac OS X 10.6.8 (10K549) > Kernel Version:Darwin 10.8.0 > > Am I out of luck? > > > ----- Original Message ----- >> From: Manfred Bergmann >> To: Jeff Barnes >> Cc: SWORD Developers' Collaboration Forum >> Sent: Wednesday, January 23, 2013 10:14 AM >> Subject: Re: [sword-devel] bindings/objc build broken >> >> If you are on Mountain Lion there may not be a 10.7 SDK. >> You can either install it from within Xcode or change the target SDK to 10.8. >> >> >> Manfred >> >> Am 23.01.2013 um 16:09 schrieb Jeff Barnes : >> >>> I opened ObjCSword.xcodeproj and tried building. It failed with the >> following build log. >>> >>> Build sword of project ObjCSword with configuration Debug >>> >>> Check dependencies >>> >>> [BEROR]error: There is no SDK with the name or path 'macosx10.7' >>> >>> >>> Requires Mountain Lion to build? I'm on Lion. >>> >>> I tried ObjCSword_preLion.xcodeproj, too. It failed with the following in >> the build log. >>> >>> >>> >>> >>> Build ObjCSword of project ObjCSword_preLion with configuration Debug >>> >>> SymLink build/Debug/ObjCSword.framework/Versions/Current A >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf A >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/Current >>> >>> SymLink build/Debug/ObjCSword.framework/Resources >> Versions/Current/Resources >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/Resources >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Resources >>> >>> SymLink build/Debug/ObjCSword.framework/ObjCSword >> Versions/Current/ObjCSword >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/ObjCSword >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/ObjCSword >>> >>> SymLink build/Debug/ObjCSword.framework/Headers Versions/Current/Headers >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/Headers >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Headers >>> >>> ProcessInfoPlistFile >> build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist Info.plist >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx >> -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/ObjCSword.h >> ObjCSword.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBible.h >> src/SwordBible.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleBook.h >> src/SwordBibleBook.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleChapter.h >> src/SwordBibleChapter.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleTextEntry.h >> src/SwordBibleTextEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBook.h >> src/SwordBook.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordCommentary.h >> src/SwordCommentary.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordDictionary.h >> src/SwordDictionary.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSource.h >> src/SwordInstallSource.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSourceController.h >> src/SwordInstallSourceController.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> pbxcp: SwordInstallSourceController.h: No such file or directory >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordKey.h >> src/SwordKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordListKey.h >> src/SwordListKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordManager.h >> src/SwordManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule.h >> src/SwordModule.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTextEntry.h >> src/SwordModuleTextEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTreeEntry.h >> src/SwordModuleTreeEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseKey.h >> src/SwordVerseKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseManager.h >> src/SwordVerseManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/VerseEnumerator.h >> src/VerseEnumerator.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Notifications.h >> src/Notifications.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/Notifications.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Configuration.h >> src/services/Configuration.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/OSXConfiguration.h >> src/services/OSXConfiguration.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule+Index.h >> src/SwordModule+Index.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordLocaleManager.h >> src/SwordLocaleManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CopyStringsFile >> build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj/InfoPlist.strings >> English.lproj/InfoPlist.strings >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv ICONV /usr/bin/iconv >>> >> /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings >> --validate --inputencoding utf-8 --outputencoding UTF-16 >> English.lproj/InfoPlist.strings --outdir >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj >>> >>> >> /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings:125: >> warning: Insecure world writable dir /opt in PATH, mode 040777 >>> >>> CpResource build/Debug/ObjCSword.framework/Versions/A/Resources/locales.d >> ../../locales.d >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/../../locales.d >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources >>> >>> ProcessPCH++ >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch >> ObjCSword_Prefix.pch normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++-header -arch x86_64 >> -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 >> -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk >> -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch >>> >>> ProcessPCH >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch >> ObjCSword_Prefix.pch normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c-header -arch x86_64 >> -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks >> -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk >> -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o >> src/SwordBible.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int +[SwordBible bookIndexForSWKey:](objc_object*, _message_ref_t*, >> sword::VerseKey*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: >> 'Book' is deprecated (declared at ../../include/versekey.h:276) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: >> 'Testament' is deprecated (declared at ../../include/versekey.h:265) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'BOOL -[SwordBible hasReference:](SwordBible*, _message_ref_t*, >> NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:186: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:189: warning: >> 'Chapter' is deprecated (declared at ../../include/versekey.h:287) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:190: warning: >> 'Verse' is deprecated (declared at ../../include/versekey.h:298) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int -[SwordBible numberOfVerseKeysForReference:](SwordBible*, >> _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:211: warning: >> 'ParseVerseList' is deprecated (declared at >> ../../include/versekey.h:452) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:213: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int -[SwordBible chaptersForBookName:](SwordBible*, _message_ref_t*, >> NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:223: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'SwordKey* -[SwordBible createKey](SwordBible*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:389: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'long int -[SwordBible entryCount](SwordBible*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:406: warning: >> 'Index' is deprecated (declared at ../../include/swmodule.h:248) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:408: warning: >> 'Index' is deprecated (declared at ../../include/swmodule.h:248) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o >> src/SwordBibleBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm: In >> function 'objc_object* -[SwordBibleBook initWithBook:](SwordBibleBook*, >> _message_ref_t*, sword::VerseMgr::Book*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:40: >> warning: 'Testament' is deprecated (declared at >> ../../include/versekey.h:265) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:41: >> warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o >> src/SwordBibleChapter.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o >> src/SwordBibleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o >> src/SwordBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o >> src/SwordCommentary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >>> from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o >> src/SwordDictionary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm: In >> function 'void -[SwordDictionary(PrivateAPI) readKeys](SwordDictionary*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:49: >> warning: 'KeyText' is deprecated (declared at >> ../../include/swmodule.h:230) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:53: >> warning: 'KeyText' is deprecated (declared at >> ../../include/swmodule.h:230) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o >> src/SwordInstallSource.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o >> src/SwordInstallSourceController.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm >> -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o >>> >>> i686-apple-darwin10-gcc-4.2.1: >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm: >> No such file or directory >>> i686-apple-darwin10-gcc-4.2.1: warning: '-x objective-c++' after >> last input file has no effect >>> i686-apple-darwin10-gcc-4.2.1: no input files >>> Command /Developer/usr/bin/gcc-4.2 failed with exit code 1 >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o >> src/SwordKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'void -[SwordKey setPersist:](SwordKey*, _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:89: warning: >> 'Persist' is deprecated (declared at ../../include/swkey.h:153) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'BOOL -[SwordKey persist](SwordKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:93: warning: >> 'Persist' is deprecated (declared at ../../include/swkey.h:146) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'int -[SwordKey error](SwordKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:97: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o >> src/SwordListKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:9: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'SwordListKey* -[SwordListKey initWithRef:headings:v11n:](SwordListKey*, >> _message_ref_t*, NSString*, BOOL, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:55: warning: >> 'Headings' is deprecated (declared at ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:59: warning: >> 'ParseVerseList' is deprecated (declared at >> ../../include/versekey.h:452) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'NSInteger -[SwordListKey numberOfVerses](SwordListKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:76: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'BOOL -[SwordListKey containsKey:](SwordListKey*, _message_ref_t*, >> SwordVerseKey*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:97: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o >> src/SwordManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm: In function >> 'void -[SwordManager(PrivateAPI) addFiltersToModule:](SwordManager*, >> _message_ref_t*, SwordModule*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:64: warning: >> 'Markup' is deprecated (declared at ../../include/swmodule.h:345) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o >> src/SwordModule.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >>> from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:20: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule mainInit](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> 'SwordModule' may not respond to '-retrieveName' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> (Messages without a matching method signature >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> will be assumed to return 'id' and accept >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> '...' as arguments.) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:127: warning: >> 'SwordModule' may not respond to '-retrieveType' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:128: warning: >> 'SwordModule' may not respond to '-retrieveDescr' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:129: warning: >> 'SwordModule' may not respond to '-retrieveLang' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule addRenderFilter:](SwordModule*, _message_ref_t*, >> SwordFilter*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:185: warning: >> 'AddRenderFilter' is deprecated (declared at >> ../../include/swmodule.h:476) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule addStripFilter:](SwordModule*, _message_ref_t*, >> SwordFilter*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:189: warning: >> 'AddStripFilter' is deprecated (declared at >> ../../include/swmodule.h:587) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveName](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:213: warning: >> 'Name' is deprecated (declared at ../../include/swmodule.h:285) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:215: warning: >> 'Name' is deprecated (declared at ../../include/swmodule.h:285) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveDescr](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:221: warning: >> 'Description' is deprecated (declared at ../../include/swmodule.h:299) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:223: warning: >> 'Description' is deprecated (declared at ../../include/swmodule.h:299) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveLang](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:229: warning: >> 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:231: warning: >> 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveType](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:237: warning: >> 'Type' is deprecated (declared at ../../include/swmodule.h:313) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:239: warning: >> 'Type' is deprecated (declared at ../../include/swmodule.h:313) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'SwordKey* -[SwordModule createKey](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:508: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule setProcessEntryAttributes:](SwordModule*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:563: warning: >> 'processEntryAttributes' is deprecated (declared at >> ../../include/swmodule.h:710) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o >> src/SwordModuleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o >> src/SwordModuleTreeEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o >> src/SwordVerseKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'SwordVerseKey* -[SwordVerseKey >> initWithSWVerseKey:makeCopy:](SwordVerseKey*, _message_ref_t*, sword::VerseKey*, >> BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:51: >> warning: incompatible Objective-C types assigning 'SwordKey*', expected >> 'SwordVerseKey*' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'SwordVerseKey* -[SwordVerseKey initWithRef:v11n:](SwordVerseKey*, >> _message_ref_t*, NSString*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:64: >> warning: incompatible Objective-C types assigning 'SwordKey*', expected >> 'SwordVerseKey*' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'int -[SwordVerseKey index](SwordVerseKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:92: error: >> 'class sword::SWKey' has no member named 'Index' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'BOOL -[SwordVerseKey headings](SwordVerseKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:96: >> warning: 'Headings' is deprecated (declared at >> ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'void -[SwordVerseKey setHeadings:](SwordVerseKey*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:100: >> warning: 'Headings' is deprecated (declared at >> ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'BOOL -[SwordVerseKey autoNormalize](SwordVerseKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:104: >> warning: 'AutoNormalize' is deprecated (declared at >> ../../include/versekey.h:380) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'void -[SwordVerseKey setAutoNormalize:](SwordVerseKey*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:108: >> warning: 'AutoNormalize' is deprecated (declared at >> ../../include/versekey.h:376) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o >> src/SwordVerseManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm: In >> function 'NSArray* -[SwordVerseManager >> booksForVersification:](SwordVerseManager*, _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm:65: >> warning: comparison between signed and unsigned integer expressions >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o >> src/VerseEnumerator.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In >> function 'NSArray* -[VerseEnumerator allObjects](VerseEnumerator*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:40: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In >> function 'NSString* -[VerseEnumerator nextObject](VerseEnumerator*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:51: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o >> src/services/OSXConfiguration.m normal x86_64 objective-c >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o >> src/services/Configuration.m normal x86_64 objective-c >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o >> src/SwordModule+Index.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm: In >> function 'NSArray* -[SwordModule(Index) performIndexSearch:](SwordModule*, >> _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm:40: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o >> src/SwordLocaleManager.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o >>> >>> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libclucene-ub.a >> build_clucene/build/result_inst/lib/libclucene-ub.a >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/build_clucene/build/result_inst/lib/libclucene-ub.a >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >>> >>> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libsword-ub.a >> build_sword/build/result_inst/lib/libsword-ub.a >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/build_sword/build/result_inst/lib/libsword-ub.a >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >>> >>> pbxcp: libsword-ub.a: No such file or directory >>> >>> >>> >>> ----- Original Message ----- >>>> From: Manfred Bergmann >>>> To: Jeff Barnes ; SWORD Developers' >> Collaboration Forum >>>> Cc: >>>> Sent: Wednesday, January 23, 2013 9:45 AM >>>> Subject: Re: [sword-devel] bindings/objc build broken >>>> >>>> Hi. >>>> >>>> The build scripts are deprecated and should be removed altogether. >>>> Try building using the ObjCSword Xcode project. >>>> I just made some code changes lately so it should still work. >>>> >>>> >>>> Manfred >>>> >>>> Am 23.01.2013 um 15:31 schrieb Jeff Barnes >> : >>>> >>>>> Thanks for the quick response, Greg. >>>>> >>>>> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >>>>> /usr/bin/autoconf >>>>> PACCPL-334LAGYA:trunk jbarne200$ which automake >>>>> /usr/bin/automake >>>>> PACCPL-334LAGYA:trunk jbarne200$ which libtool >>>>> /usr/bin/libtool >>>>> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >>>>> /usr/bin/aclocal >>>>> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >>>>> /usr/bin/autoheader >>>>> >>>>> I was originally missing pkg-config. I installed it (for some >> reason the >>>> mac flavor is installed in /opt) and created a symbolic link to it in >> /usr/bin. >>>> I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that >> point, I >>>> was able to build using trunk/autogen.sh. >>>>> >>>>> Still not able to build using >> bindings/objc/build_sword/build_mac_sword.sh. >>>> I get the error mentioned in my original post. >>>>> >>>>> It might help mac users to have an environment check script (I >> still >>>> don't have a full command of gnu on mac). Something like the >> following might >>>> be useful. >>>>> >>>>> #!/bin/sh >>>>> echo "Checking build environment" >>>>> autoconf --help >/dev/null || exit $? >>>>> automake --help >/dev/null || exit $? >>>>> ... >>>>> etc >>>>> >>>>> Jeff >>>>> >>>>> >>>>>> ________________________________ >>>>>> From: Greg Hellings >>>>>> To: Jeff Barnes ; SWORD >> Developers' >>>> Collaboration Forum >>>>>> Sent: Wednesday, January 23, 2013 8:49 AM >>>>>> Subject: Re: [sword-devel] bindings/objc build broken >>>>>> >>>>>> >>>>>> The Obj-C bindings have not been updated since Troy's major >> commit >>>> to deprecate methods and the like. However, the error you're seeing >> appears >>>> to be a result of missing some of the autofoo material that you need. >> Do you >>>> have any information on the state of your autotools package? That might >> help the >>>> Obj-C maintainer with your problem. >>>>>> >>>>>> >>>>>> --Greg >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes >>>> wrote: >>>>>> >>>>>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. >> Changed >>>> to bindings/objc. >>>>>>> >>>>>>> 1) The bindings/objc/README instructions are inaccurate. >> There is >>>> no Makefile in build_sword. >>>>>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>>>>> >>>>>>> $ cd build_clucene >>>>>>> >>>>>>> $ make release-fat >>>>>>> ... >>>>>>> looks like successful build for 3 platforms >>>>>>> >>>>>>> $ cd ../build_sword >>>>>>> $ ./build_mac_sword.sh -a fat -c >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> ./configure: line 15671: syntax error near unexpected token >> >>>> `CLUCENE2,' >>>>>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, >>>> libclucene-core >= 2.3,,true)' >>>>>>> >>>>>>> $ pkg-config --cflags --libs libclucene-core >>>>>>> -I/usr/local/include -I/usr/local/include/CLucene/ext >>>> -L/usr/local/lib/ -lclucene-core >>>>>>> >>>>>>> $ which pkg-config >>>>>>> /usr/bin/pkg-config >>>>>>> >>>>>>> System Version:Mac OS X 10.6.8 (10K549) >>>>>>> ... >>>>>>> Model Name:MacBook Pro >>>>>>> Model Identifier:MacBookPro6,2 >>>>>>> Processor Name:Intel Core i5 >>>>>>> >>>>>>> Any help appreciated. >>>>>>> >>>>>>> Jeff >>>>>>> >>>>>>> _______________________________________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above >> page >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>> >> From manfred.bergmann at me.com Wed Jan 23 10:05:20 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 18:05:20 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: Just out of curiosity, what do you need the objc wrappers for? Manfred Am 23.01.2013 um 16:24 schrieb Jeff Barnes : > Oops. I'm not on Lion... > > System Software Overview: > > System Version:Mac OS X 10.6.8 (10K549) > Kernel Version:Darwin 10.8.0 > > Am I out of luck? > > > ----- Original Message ----- >> From: Manfred Bergmann >> To: Jeff Barnes >> Cc: SWORD Developers' Collaboration Forum >> Sent: Wednesday, January 23, 2013 10:14 AM >> Subject: Re: [sword-devel] bindings/objc build broken >> >> If you are on Mountain Lion there may not be a 10.7 SDK. >> You can either install it from within Xcode or change the target SDK to 10.8. >> >> >> Manfred >> >> Am 23.01.2013 um 16:09 schrieb Jeff Barnes : >> >>> I opened ObjCSword.xcodeproj and tried building. It failed with the >> following build log. >>> >>> Build sword of project ObjCSword with configuration Debug >>> >>> Check dependencies >>> >>> [BEROR]error: There is no SDK with the name or path 'macosx10.7' >>> >>> >>> Requires Mountain Lion to build? I'm on Lion. >>> >>> I tried ObjCSword_preLion.xcodeproj, too. It failed with the following in >> the build log. >>> >>> >>> >>> >>> Build ObjCSword of project ObjCSword_preLion with configuration Debug >>> >>> SymLink build/Debug/ObjCSword.framework/Versions/Current A >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf A >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/Current >>> >>> SymLink build/Debug/ObjCSword.framework/Resources >> Versions/Current/Resources >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/Resources >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Resources >>> >>> SymLink build/Debug/ObjCSword.framework/ObjCSword >> Versions/Current/ObjCSword >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/ObjCSword >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/ObjCSword >>> >>> SymLink build/Debug/ObjCSword.framework/Headers Versions/Current/Headers >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /bin/ln -sf Versions/Current/Headers >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Headers >>> >>> ProcessInfoPlistFile >> build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist Info.plist >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> builtin-infoPlistUtility Info.plist -expandbuildsettings -platform macosx >> -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/Info.plist >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/ObjCSword.h >> ObjCSword.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBible.h >> src/SwordBible.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleBook.h >> src/SwordBibleBook.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleChapter.h >> src/SwordBibleChapter.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBibleTextEntry.h >> src/SwordBibleTextEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordBook.h >> src/SwordBook.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordCommentary.h >> src/SwordCommentary.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordDictionary.h >> src/SwordDictionary.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSource.h >> src/SwordInstallSource.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordInstallSourceController.h >> src/SwordInstallSourceController.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> pbxcp: SwordInstallSourceController.h: No such file or directory >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordKey.h >> src/SwordKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordListKey.h >> src/SwordListKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordManager.h >> src/SwordManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule.h >> src/SwordModule.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTextEntry.h >> src/SwordModuleTextEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModuleTreeEntry.h >> src/SwordModuleTreeEntry.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseKey.h >> src/SwordVerseKey.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordVerseManager.h >> src/SwordVerseManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/VerseEnumerator.h >> src/VerseEnumerator.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Notifications.h >> src/Notifications.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/Notifications.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader build/Debug/ObjCSword.framework/Versions/A/Headers/Configuration.h >> src/services/Configuration.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/OSXConfiguration.h >> src/services/OSXConfiguration.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordModule+Index.h >> src/SwordModule+Index.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CpHeader >> build/Debug/ObjCSword.framework/Versions/A/Headers/SwordLocaleManager.h >> src/SwordLocaleManager.h >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.h >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Headers >>> >>> CopyStringsFile >> build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj/InfoPlist.strings >> English.lproj/InfoPlist.strings >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv ICONV /usr/bin/iconv >>> >> /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings >> --validate --inputencoding utf-8 --outputencoding UTF-16 >> English.lproj/InfoPlist.strings --outdir >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources/English.lproj >>> >>> >> /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings:125: >> warning: Insecure world writable dir /opt in PATH, mode 040777 >>> >>> CpResource build/Debug/ObjCSword.framework/Versions/A/Resources/locales.d >> ../../locales.d >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/../../locales.d >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Resources >>> >>> ProcessPCH++ >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch >> ObjCSword_Prefix.pch normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++-header -arch x86_64 >> -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 >> -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk >> -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch.gch >>> >>> ProcessPCH >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch >> ObjCSword_Prefix.pch normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c-header -arch x86_64 >> -fmessage-length=0 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks >> -O0 -Wreturn-type -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk >> -fobjc-gc-only -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -c /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword_Prefix.pch -o >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch.gch >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o >> src/SwordBible.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBible.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int +[SwordBible bookIndexForSWKey:](objc_object*, _message_ref_t*, >> sword::VerseKey*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: >> 'Book' is deprecated (declared at ../../include/versekey.h:276) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:99: warning: >> 'Testament' is deprecated (declared at ../../include/versekey.h:265) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'BOOL -[SwordBible hasReference:](SwordBible*, _message_ref_t*, >> NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:186: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:189: warning: >> 'Chapter' is deprecated (declared at ../../include/versekey.h:287) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:190: warning: >> 'Verse' is deprecated (declared at ../../include/versekey.h:298) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int -[SwordBible numberOfVerseKeysForReference:](SwordBible*, >> _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:211: warning: >> 'ParseVerseList' is deprecated (declared at >> ../../include/versekey.h:452) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:213: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'int -[SwordBible chaptersForBookName:](SwordBible*, _message_ref_t*, >> NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:223: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'SwordKey* -[SwordBible createKey](SwordBible*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:389: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm: In function >> 'long int -[SwordBible entryCount](SwordBible*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:406: warning: >> 'Index' is deprecated (declared at ../../include/swmodule.h:248) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBible.mm:408: warning: >> 'Index' is deprecated (declared at ../../include/swmodule.h:248) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o >> src/SwordBibleBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleBook.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm: In >> function 'objc_object* -[SwordBibleBook initWithBook:](SwordBibleBook*, >> _message_ref_t*, sword::VerseMgr::Book*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:40: >> warning: 'Testament' is deprecated (declared at >> ../../include/versekey.h:265) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleBook.mm:41: >> warning: 'Book' is deprecated (declared at ../../include/versekey.h:276) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o >> src/SwordBibleChapter.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleChapter.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleChapter.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o >> src/SwordBibleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBibleTextEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBibleTextEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o >> src/SwordBook.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordBook.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordBook.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o >> src/SwordCommentary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordCommentary.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >>> from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o >> src/SwordDictionary.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordDictionary.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm: In >> function 'void -[SwordDictionary(PrivateAPI) readKeys](SwordDictionary*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:49: >> warning: 'KeyText' is deprecated (declared at >> ../../include/swmodule.h:230) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordDictionary.mm:53: >> warning: 'KeyText' is deprecated (declared at >> ../../include/swmodule.h:230) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o >> src/SwordInstallSource.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSource.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSource.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o >> src/SwordInstallSourceController.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm >> -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordInstallSourceController.o >>> >>> i686-apple-darwin10-gcc-4.2.1: >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordInstallSourceController.mm: >> No such file or directory >>> i686-apple-darwin10-gcc-4.2.1: warning: '-x objective-c++' after >> last input file has no effect >>> i686-apple-darwin10-gcc-4.2.1: no input files >>> Command /Developer/usr/bin/gcc-4.2 failed with exit code 1 >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o >> src/SwordKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordKey.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'void -[SwordKey setPersist:](SwordKey*, _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:89: warning: >> 'Persist' is deprecated (declared at ../../include/swkey.h:153) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'BOOL -[SwordKey persist](SwordKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:93: warning: >> 'Persist' is deprecated (declared at ../../include/swkey.h:146) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm: In function >> 'int -[SwordKey error](SwordKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordKey.mm:97: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o >> src/SwordListKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordListKey.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:9: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'SwordListKey* -[SwordListKey initWithRef:headings:v11n:](SwordListKey*, >> _message_ref_t*, NSString*, BOOL, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:55: warning: >> 'Headings' is deprecated (declared at ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:59: warning: >> 'ParseVerseList' is deprecated (declared at >> ../../include/versekey.h:452) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'NSInteger -[SwordListKey numberOfVerses](SwordListKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:76: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm: In function >> 'BOOL -[SwordListKey containsKey:](SwordListKey*, _message_ref_t*, >> SwordVerseKey*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordListKey.mm:97: warning: >> 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o >> src/SwordManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordManager.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:14: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm: In function >> 'void -[SwordManager(PrivateAPI) addFiltersToModule:](SwordManager*, >> _message_ref_t*, SwordModule*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordManager.mm:64: warning: >> 'Markup' is deprecated (declared at ../../include/swmodule.h:345) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o >> src/SwordModule.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule.o >>> >>> In file included from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordCommentary.h:15, >>> from >> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:20: >>> /Users/jbarne200/sword/trunk/bindings/objc/ObjCSword.h:26:48: error: >> ObjCSword/SwordInstallSourceManager.h: No such file or directory >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule mainInit](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> 'SwordModule' may not respond to '-retrieveName' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> (Messages without a matching method signature >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> will be assumed to return 'id' and accept >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:126: warning: >> '...' as arguments.) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:127: warning: >> 'SwordModule' may not respond to '-retrieveType' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:128: warning: >> 'SwordModule' may not respond to '-retrieveDescr' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:129: warning: >> 'SwordModule' may not respond to '-retrieveLang' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule addRenderFilter:](SwordModule*, _message_ref_t*, >> SwordFilter*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:185: warning: >> 'AddRenderFilter' is deprecated (declared at >> ../../include/swmodule.h:476) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule addStripFilter:](SwordModule*, _message_ref_t*, >> SwordFilter*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:189: warning: >> 'AddStripFilter' is deprecated (declared at >> ../../include/swmodule.h:587) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveName](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:213: warning: >> 'Name' is deprecated (declared at ../../include/swmodule.h:285) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:215: warning: >> 'Name' is deprecated (declared at ../../include/swmodule.h:285) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveDescr](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:221: warning: >> 'Description' is deprecated (declared at ../../include/swmodule.h:299) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:223: warning: >> 'Description' is deprecated (declared at ../../include/swmodule.h:299) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveLang](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:229: warning: >> 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:231: warning: >> 'Lang' is deprecated (declared at ../../include/swmodule.h:353) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'NSString* -[SwordModule retrieveType](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:237: warning: >> 'Type' is deprecated (declared at ../../include/swmodule.h:313) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:239: warning: >> 'Type' is deprecated (declared at ../../include/swmodule.h:313) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'SwordKey* -[SwordModule createKey](SwordModule*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:508: warning: >> 'CreateKey' is deprecated (declared at ../../include/swmodule.h:400) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm: In function >> 'void -[SwordModule setProcessEntryAttributes:](SwordModule*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule.mm:563: warning: >> 'processEntryAttributes' is deprecated (declared at >> ../../include/swmodule.h:710) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o >> src/SwordModuleTextEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTextEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTextEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o >> src/SwordModuleTreeEntry.m normal x86_64 objective-c com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModuleTreeEntry.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModuleTreeEntry.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o >> src/SwordVerseKey.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseKey.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'SwordVerseKey* -[SwordVerseKey >> initWithSWVerseKey:makeCopy:](SwordVerseKey*, _message_ref_t*, sword::VerseKey*, >> BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:51: >> warning: incompatible Objective-C types assigning 'SwordKey*', expected >> 'SwordVerseKey*' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'SwordVerseKey* -[SwordVerseKey initWithRef:v11n:](SwordVerseKey*, >> _message_ref_t*, NSString*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:64: >> warning: incompatible Objective-C types assigning 'SwordKey*', expected >> 'SwordVerseKey*' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'int -[SwordVerseKey index](SwordVerseKey*, _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:92: error: >> 'class sword::SWKey' has no member named 'Index' >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'BOOL -[SwordVerseKey headings](SwordVerseKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:96: >> warning: 'Headings' is deprecated (declared at >> ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'void -[SwordVerseKey setHeadings:](SwordVerseKey*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:100: >> warning: 'Headings' is deprecated (declared at >> ../../include/versekey.h:392) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'BOOL -[SwordVerseKey autoNormalize](SwordVerseKey*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:104: >> warning: 'AutoNormalize' is deprecated (declared at >> ../../include/versekey.h:380) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm: In >> function 'void -[SwordVerseKey setAutoNormalize:](SwordVerseKey*, >> _message_ref_t*, BOOL)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseKey.mm:108: >> warning: 'AutoNormalize' is deprecated (declared at >> ../../include/versekey.h:376) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o >> src/SwordVerseManager.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordVerseManager.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm: In >> function 'NSArray* -[SwordVerseManager >> booksForVersification:](SwordVerseManager*, _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordVerseManager.mm:65: >> warning: comparison between signed and unsigned integer expressions >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o >> src/VerseEnumerator.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/VerseEnumerator.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In >> function 'NSArray* -[VerseEnumerator allObjects](VerseEnumerator*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:40: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm: In >> function 'NSString* -[VerseEnumerator nextObject](VerseEnumerator*, >> _message_ref_t*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/VerseEnumerator.mm:51: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o >> src/services/OSXConfiguration.m normal x86_64 objective-c >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/OSXConfiguration.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/OSXConfiguration.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o >> src/services/Configuration.m normal x86_64 objective-c >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c -arch x86_64 -fmessage-length=0 >> -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include >>> -I../../include -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-fwjlhelxkjiczoazuygbaritmivm/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/services/Configuration.m -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/Configuration.o >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o >> src/SwordModule+Index.mm normal x86_64 objective-c++ com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordModule+Index.o >>> >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm: In >> function 'NSArray* -[SwordModule(Index) performIndexSearch:](SwordModule*, >> _message_ref_t*, NSString*)': >>> /Users/jbarne200/sword/trunk/bindings/objc/src/SwordModule+Index.mm:40: >> warning: 'Error' is deprecated (declared at ../../include/swkey.h:159) >>> >>> CompileC >> build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o >> src/SwordLocaleManager.mm normal x86_64 objective-c++ >> com.apple.compilers.gcc.4_2 >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> setenv LANG en_US.US-ASCII >>> /Developer/usr/bin/gcc-4.2 -x objective-c++ -arch x86_64 -fmessage-length=0 >> -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wreturn-type >> -Wunused-variable -isysroot /Developer/SDKs/MacOSX10.5.sdk -fobjc-gc-only >> -mmacosx-version-min=10.5 -gdwarf-2 -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-generated-files.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-own-target-headers.hmap >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-all-target-headers.hmap >> -iquote >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/ObjCSword-project-headers.hmap >> -Wall -F/Users/jbarne200/sword/trunk/bindings/objc/build/Debug >> -F/Developer/Library/Frameworks >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/Debug/include -I../../include >>> -I../../include/internal -I../../include/internal/regex >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources/x86_64 >> -I/Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/DerivedSources >> -DDEBUG -include >> /var/folders/Gp/GpnCyNt6GrS5YrGwwbsdvIhQnjY/-Caches-/com.apple.Xcode.1264373497/SharedPrecompiledHeaders/ObjCSword_Prefix-cjqhjkokaapigkedxvcjayofuzgb/ObjCSword_Prefix.pch >> -c /Users/jbarne200/sword/trunk/bindings/objc/src/SwordLocaleManager.mm -o >> /Users/jbarne200/sword/trunk/bindings/objc/build/ObjCSword_preLion.build/Debug/ObjCSword.build/Objects-normal/x86_64/SwordLocaleManager.o >>> >>> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libclucene-ub.a >> build_clucene/build/result_inst/lib/libclucene-ub.a >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/build_clucene/build/result_inst/lib/libclucene-ub.a >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >>> >>> PBXCp build/Debug/ObjCSword.framework/Versions/A/Frameworks/libsword-ub.a >> build_sword/build/result_inst/lib/libsword-ub.a >>> cd /Users/jbarne200/sword/trunk/bindings/objc >>> /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp >> -exclude .DS_Store -exclude CVS -exclude .svn -resolve-src-symlinks >> /Users/jbarne200/sword/trunk/bindings/objc/build_sword/build/result_inst/lib/libsword-ub.a >> /Users/jbarne200/sword/trunk/bindings/objc/build/Debug/ObjCSword.framework/Versions/A/Frameworks >>> >>> pbxcp: libsword-ub.a: No such file or directory >>> >>> >>> >>> ----- Original Message ----- >>>> From: Manfred Bergmann >>>> To: Jeff Barnes ; SWORD Developers' >> Collaboration Forum >>>> Cc: >>>> Sent: Wednesday, January 23, 2013 9:45 AM >>>> Subject: Re: [sword-devel] bindings/objc build broken >>>> >>>> Hi. >>>> >>>> The build scripts are deprecated and should be removed altogether. >>>> Try building using the ObjCSword Xcode project. >>>> I just made some code changes lately so it should still work. >>>> >>>> >>>> Manfred >>>> >>>> Am 23.01.2013 um 15:31 schrieb Jeff Barnes >> : >>>> >>>>> Thanks for the quick response, Greg. >>>>> >>>>> PACCPL-334LAGYA:trunk jbarne200$ which autoconf >>>>> /usr/bin/autoconf >>>>> PACCPL-334LAGYA:trunk jbarne200$ which automake >>>>> /usr/bin/automake >>>>> PACCPL-334LAGYA:trunk jbarne200$ which libtool >>>>> /usr/bin/libtool >>>>> PACCPL-334LAGYA:trunk jbarne200$ which aclocal >>>>> /usr/bin/aclocal >>>>> PACCPL-334LAGYA:trunk jbarne200$ which autoheader >>>>> /usr/bin/autoheader >>>>> >>>>> I was originally missing pkg-config. I installed it (for some >> reason the >>>> mac flavor is installed in /opt) and created a symbolic link to it in >> /usr/bin. >>>> I also created a sym link to /usr/bin/glibtoolize in /usr/bin. At that >> point, I >>>> was able to build using trunk/autogen.sh. >>>>> >>>>> Still not able to build using >> bindings/objc/build_sword/build_mac_sword.sh. >>>> I get the error mentioned in my original post. >>>>> >>>>> It might help mac users to have an environment check script (I >> still >>>> don't have a full command of gnu on mac). Something like the >> following might >>>> be useful. >>>>> >>>>> #!/bin/sh >>>>> echo "Checking build environment" >>>>> autoconf --help >/dev/null || exit $? >>>>> automake --help >/dev/null || exit $? >>>>> ... >>>>> etc >>>>> >>>>> Jeff >>>>> >>>>> >>>>>> ________________________________ >>>>>> From: Greg Hellings >>>>>> To: Jeff Barnes ; SWORD >> Developers' >>>> Collaboration Forum >>>>>> Sent: Wednesday, January 23, 2013 8:49 AM >>>>>> Subject: Re: [sword-devel] bindings/objc build broken >>>>>> >>>>>> >>>>>> The Obj-C bindings have not been updated since Troy's major >> commit >>>> to deprecate methods and the like. However, the error you're seeing >> appears >>>> to be a result of missing some of the autofoo material that you need. >> Do you >>>> have any information on the state of your autotools package? That might >> help the >>>> Obj-C maintainer with your problem. >>>>>> >>>>>> >>>>>> --Greg >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jan 23, 2013 at 7:38 AM, Jeff Barnes >>>> wrote: >>>>>> >>>>>> Did a fresh checkout of https://crosswire.org/svn/sword/trunk. >> Changed >>>> to bindings/objc. >>>>>>> >>>>>>> 1) The bindings/objc/README instructions are inaccurate. >> There is >>>> no Makefile in build_sword. >>>>>>> 2) The build breaks in build_sword/build_mac_sword.sh. >>>>>>> >>>>>>> $ cd build_clucene >>>>>>> >>>>>>> $ make release-fat >>>>>>> ... >>>>>>> looks like successful build for 3 platforms >>>>>>> >>>>>>> $ cd ../build_sword >>>>>>> $ ./build_mac_sword.sh -a fat -c >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> ./configure: line 15671: syntax error near unexpected token >> >>>> `CLUCENE2,' >>>>>>> ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, >>>> libclucene-core >= 2.3,,true)' >>>>>>> >>>>>>> $ pkg-config --cflags --libs libclucene-core >>>>>>> -I/usr/local/include -I/usr/local/include/CLucene/ext >>>> -L/usr/local/lib/ -lclucene-core >>>>>>> >>>>>>> $ which pkg-config >>>>>>> /usr/bin/pkg-config >>>>>>> >>>>>>> System Version:Mac OS X 10.6.8 (10K549) >>>>>>> ... >>>>>>> Model Name:MacBook Pro >>>>>>> Model Identifier:MacBookPro6,2 >>>>>>> Processor Name:Intel Core i5 >>>>>>> >>>>>>> Any help appreciated. >>>>>>> >>>>>>> Jeff >>>>>>> >>>>>>> _______________________________________________ >>>>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>>>> Instructions to unsubscribe/change your settings at above >> page >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> sword-devel mailing list: sword-devel at crosswire.org >>>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>>> Instructions to unsubscribe/change your settings at above page >>>> >> From thulester at gmail.com Wed Jan 23 10:52:49 2013 From: thulester at gmail.com (Andrew Thule) Date: Wed, 23 Jan 2013 12:52:49 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: <20130123160231.213410@gmx.net> Message-ID: Peter, DM, Thanks for your response. I wasn't being critical and I agree. There are Pros and Cons either way (resource usage and download time being considerations) as you point out. I also agree it's ultimately it's up to the repo administrator and the user, to decide for themselves what works best for them. I happen to like having the index included as part of the repo, because I'm not limited by resources, and I don't mind the wait. Regardless, it is still a matter of preference (based upon considerations, such as the ones you cite). ~A On Wednesday, January 23, 2013, DM Smith wrote: > > On Jan 23, 2013, at 11:02 AM, "Peter von Kaehne" > > wrote: > > > > >> Von: Andrew Thule > > > > >> The nice thing about when > >> repo administrators do this, is when you get a module from that repo, > you > >> also automatically get the lucene index. > > > > The reason that this is not done are manifold - including that sword and > jsword indices are different, that not all platforms have the same > lucene/clucene incarnation etc. > > > > Most users are better off not to use downloaded indices, but to create > indices suitable for their specific frontend. > > To add to what Peter said, this mailing list's archives have extensive > discussion on why we don't do this and why we have done it for mobile > devices (only PocketSword and AndBible, and specific to them only). > > Also, the transfer time for a lucene index exceeds the time of a recent > computer to build them, e.g. my laptop. As a Bible Desktop user, I'd really > rather not transfer an index that is unusable by Bible Desktop. > > In Him, > DM > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Wed Jan 23 11:18:07 2013 From: refdoc at gmx.net (Peter von Kaehne) Date: Wed, 23 Jan 2013 19:18:07 +0100 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: <20130123160231.213410@gmx.net> Message-ID: <20130123181807.85590@gmx.net> > Von: Andrew Thule > There are Pros and Cons either way (resource usage and download time > being considerations) as you point out. There are no pros and only contras. And I certainly have not pointed out any pros. Nor has DM. Please stop using my name as supposedly in agreement with you. I find this offensive. FWIW - If you run a repo for anyone other than yourself with indeces included, you will create a significant risk of malfunction. For anyone other than the user of the specific version of libsword and clucene. As such no one expects from you anything anymore, so, further explanations are probably pointless. From chris at burrell.me.uk Wed Jan 23 11:42:53 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Wed, 23 Jan 2013 18:42:53 +0000 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <20130123181807.85590@gmx.net> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> Message-ID: To add to the discussion. Step ships data files and later indexes as part of the installation of software plus automatically after installation of any module. We considered shipping indexes but decided against it. This is because indexes can become corrupt quite easily and can be incompatible for no obvious reasons. We also want to be able to update data later with a lot of people having bad Internet connections. Since we're using Lucene as our data store as well as our indexing engine we need to ship most of the text data anyway. So functionality needs to be there anyway to manage indexing. As DM says it can often be done in background very fast. Chris On 23 Jan 2013 18:20, "Peter von Kaehne" wrote: > > > Von: Andrew Thule > > There are Pros and Cons either way (resource usage and download time > > being considerations) as you point out. > > There are no pros and only contras. And I certainly have not pointed out > any pros. Nor has DM. Please stop using my name as supposedly in agreement > with you. I find this offensive. > > FWIW - If you run a repo for anyone other than yourself with indeces > included, you will create a significant risk of malfunction. For anyone > other than the user of the specific version of libsword and clucene. > > As such no one expects from you anything anymore, so, further explanations > are probably pointless. > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmsmith at crosswire.org Wed Jan 23 11:50:28 2013 From: dmsmith at crosswire.org (DM Smith) Date: Wed, 23 Jan 2013 13:50:28 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: <20130123160231.213410@gmx.net> Message-ID: <3EAFC086-B96A-4357-877E-6DFF7A077ED6@crosswire.org> The repo admin needs to decide what is best for all users of the repo. For example, they cannot assume that Xiphos (to pick out one SWORD application) is the same version for every user. And even if it is the same version, they cannot assume that lucene is the same. So, having the indexes in a public repo is a bad idea. In a private repo, it doesn't matter. To repeat earlier threads of what can cause indices to become invalid: New version of Unicode. For JSword, this is based upon the version of Java. A Java upgrade requires indices to be rebuilt. (Note: JSword and SWORD cannot share indices.) For Windows, I think it is part of the OS. If so XP, Vista, Win 7 and Win 8 clients may have different Unicode. The same idea applies to Linux. To the extent that ICU is used to provide Unicode, the same applies. The app can be compiled w or w/o ICU. The version of the SWORD lib has to be the same. The version of Lucene has to be the same. There is no mechanism in SWORD or JSword to know when an index is not valid and in need of being rebuilt. Short of an application having tight control over the index (such as PocketSword, AndBible and STEP) it does not make sense to have indices stored in the repo. Even then, the indices should be stored in parallel, not with the module. The only reason I see to have it otherwise is if the repo is private and personal. Hope this clarifies. In Him, DM On Jan 23, 2013, at 12:52 PM, Andrew Thule wrote: > Peter, DM, Thanks for your response. I wasn't being critical and I agree. There are Pros and Cons either way (resource usage and download time being considerations) as you point out. > > I also agree it's ultimately it's up to the repo administrator and the user, to decide for themselves what works best for them. I happen to like having the index included as part of the repo, because I'm not limited by resources, and I don't mind the wait. > > Regardless, it is still a matter of preference (based upon considerations, such as the ones you cite). > ~A > > On Wednesday, January 23, 2013, DM Smith wrote: > > On Jan 23, 2013, at 11:02 AM, "Peter von Kaehne" wrote: > > > > >> Von: Andrew Thule > > > >> The nice thing about when > >> repo administrators do this, is when you get a module from that repo, you > >> also automatically get the lucene index. > > > > The reason that this is not done are manifold - including that sword and jsword indices are different, that not all platforms have the same lucene/clucene incarnation etc. > > > > Most users are better off not to use downloaded indices, but to create indices suitable for their specific frontend. > > To add to what Peter said, this mailing list's archives have extensive discussion on why we don't do this and why we have done it for mobile devices (only PocketSword and AndBible, and specific to them only). > > Also, the transfer time for a lucene index exceeds the time of a recent computer to build them, e.g. my laptop. As a Bible Desktop user, I'd really rather not transfer an index that is unusable by Bible Desktop. > > In Him, > DM > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 23 12:08:27 2013 From: thulester at gmail.com (Andrew Thule) Date: Wed, 23 Jan 2013 14:08:27 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <20130123181807.85590@gmx.net> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> Message-ID: Peter, if I offended you, I hope you'll forgive me. ~A On Wednesday, January 23, 2013, Peter von Kaehne wrote: > > > Von: Andrew Thule > > > There are Pros and Cons either way (resource usage and download time > > being considerations) as you point out. > > There are no pros and only contras. And I certainly have not pointed out > any pros. Nor has DM. Please stop using my name as supposedly in agreement > with you. I find this offensive. > > FWIW - If you run a repo for anyone other than yourself with indeces > included, you will create a significant risk of malfunction. For anyone > other than the user of the specific version of libsword and clucene. > > As such no one expects from you anything anymore, so, further explanations > are probably pointless. > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manfred.bergmann at me.com Wed Jan 23 12:21:09 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 20:21:09 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: Am 23.01.2013 um 19:41 schrieb "Barnes, Jeffrey" : > > On Jan 23, 2013, at 12:05:20PM, Manfred Bergmann wrote: > >> Just out of curiosity, what do you need the objc wrappers for? >> > > Just want to play around with the API. Develop a simple client. Curiosity while I learn to code in Objective-C/Cocoa. OK. Can you upgrade to Lion at least? That would probably be the easiest because the this Xcode project is maintained. Manfred From manfred.bergmann at me.com Wed Jan 23 14:20:22 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Wed, 23 Jan 2013 22:20:22 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: Am 23.01.2013 um 21:54 schrieb "Barnes, Jeffrey" : > > On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann wrote: > >> >> OK. Can you upgrade to Lion at least? >> That would probably be the easiest because the this Xcode project is maintained. >> > > Last night, while we were asleep, my wife poked me in the eye when she rolled over. I upgraded to Mountain Lion today. I must say, the poke in the eye was less painful. It only lasted a few minutes. > > Gcc? gone > Java? gone > XCode? gone > Subversion client? gone > XWindows? > > Well, you get the idea. But now, I've got the new Xcode and I'm building ObjCSword. So far it's been about 15 minutes? (Not counting the 2 hour download / install / fix of Mountain Lion) > > More to follow. > Jeff > Well, you know how Apple is. Much changes, especially over on two major versions. Many things have their advantages. Installing Xcode over App Store is pretty much painless (except the download). You get gcc, subversion, git and many other goodies once you've installed it. The OS X Java port is now maintained by Oracle which IMO is a good thing as well. Manfred From niccarter at mac.com Wed Jan 23 18:31:29 2013 From: niccarter at mac.com (Nic Carter) Date: Thu, 24 Jan 2013 12:31:29 +1100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: <7AB05CA9-707E-43B4-84DB-931B5E17D5ED@mac.com> Looks like the pre-Lion project hadn't been updated in a long time and so didn't have any newly required headers added to it (which you can see from the build log you pasted in a previous email). You could also look at the PocketSword source to get another idea of how to go about compiling things? As for your experience upgrading from Snow Leopard to Mountain Lion, I'm guessing all is working well for you now? XWindows is also now directly maintained by the developers, rather than having Apple as the middle-man (same as Java). If you're lucky, you won't need to ever use Java. XWindows, however, is much more useful to have around. :D Oh, one last thing: once you've installed Xcode you'll need to install the command-line tools, which you do via the Xcode Preferences (under the Downloads tab). Hope that helps? :) Thanks, ybic nic... :) PS: oh, I'm on Mountain Lion, and so I know all the PocketSword stuff compiles on it. But PocketSword is only for iOS, so it's up to you if you're wanting to play around with that? :) On 24/01/2013, at 8:20 AM, Manfred Bergmann wrote: > > Am 23.01.2013 um 21:54 schrieb "Barnes, Jeffrey" : > >> >> On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann wrote: >> >>> >>> OK. Can you upgrade to Lion at least? >>> That would probably be the easiest because the this Xcode project is maintained. >>> >> >> Last night, while we were asleep, my wife poked me in the eye when she rolled over. I upgraded to Mountain Lion today. I must say, the poke in the eye was less painful. It only lasted a few minutes. >> >> Gcc? gone >> Java? gone >> XCode? gone >> Subversion client? gone >> XWindows? >> >> Well, you get the idea. But now, I've got the new Xcode and I'm building ObjCSword. So far it's been about 15 minutes? (Not counting the 2 hour download / install / fix of Mountain Lion) >> >> More to follow. >> Jeff >> > > Well, you know how Apple is. Much changes, especially over on two major versions. > Many things have their advantages. Installing Xcode over App Store is pretty much painless (except the download). You get gcc, subversion, git and many other goodies once you've installed it. > The OS X Java port is now maintained by Oracle which IMO is a good thing as well. > > > Manfred > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From niccarter at mac.com Wed Jan 23 18:43:09 2013 From: niccarter at mac.com (Nic Carter) Date: Thu, 24 Jan 2013 12:43:09 +1100 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <20130123181807.85590@gmx.net> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> Message-ID: <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> My suggestion would be to avoid pre-built indices. However, given I'm the one who first went about making them, I think there are pros in certain situations. :P In my situation, I get to be gatekeeper over the entire solution (PocketSword), where users cannot change the version of clucene or libsword behind my back. And so I can be aware of when things might break (& increment my "v1" bit of the download URL of the indices). BTW, I would strongly suggest that no one else use either the and-bible or PocketSword pre-built indices due to incompatibilities that have been explained in other posts. :) I'd also strongly suggest that no one else creates new ones for another platform, unless it's absolutely necessary. They are messy, as you can probably gather from all these posts! :) Thanks, ybic nic... :) On 24/01/2013, at 5:18 AM, Peter von Kaehne wrote: > >> Von: Andrew Thule >> There are Pros and Cons either way (resource usage and download time >> being considerations) as you point out. > > There are no pros and only contras. And I certainly have not pointed out any pros. Nor has DM. Please stop using my name as supposedly in agreement with you. I find this offensive. > > FWIW - If you run a repo for anyone other than yourself with indeces included, you will create a significant risk of malfunction. For anyone other than the user of the specific version of libsword and clucene. > > As such no one expects from you anything anymore, so, further explanations are probably pointless. > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From jbarnesweb at yahoo.com Wed Jan 23 21:30:30 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Wed, 23 Jan 2013 23:30:30 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <7AB05CA9-707E-43B4-84DB-931B5E17D5ED@mac.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <7AB05CA9-707E-43B4-84DB-931B5E17D5ED@mac.com> Message-ID: On Jan 23, 2013, at 8:31:29PM, Nic Carter wrote: > You could also look at the PocketSword source to get another idea of how to go about compiling things? > The reason I posted to sword-devel is because they own the broken build. Whoever is the objc bindings build maintainer should fix it. From greg.hellings at gmail.com Wed Jan 23 21:36:30 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Wed, 23 Jan 2013 22:36:30 -0600 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <7AB05CA9-707E-43B4-84DB-931B5E17D5ED@mac.com> Message-ID: On Wed, Jan 23, 2013 at 10:30 PM, Barnes, Jeffrey wrote: > > On Jan 23, 2013, at 8:31:29PM, Nic Carter wrote: > > > You could also look at the PocketSword source to get another idea of how > to go about compiling things? > > > > The reason I posted to sword-devel is because they own the broken build. > Whoever is the objc bindings build maintainer should fix it. > Well that's Manfred and Nic (more Manfred from what I see in the commit logs, but both Pocket Sword and Eloquent are based on getting SWORD to build in XCode and I know the two have worked together on it), so you've come to the right place! --Greg > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Wed Jan 23 21:55:45 2013 From: thulester at gmail.com (Andrew Thule) Date: Wed, 23 Jan 2013 23:55:45 -0500 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> Message-ID: Thanks for making them .. It is appreciated! ... I find them incredibly useful (and I was surprised they worked by way of a repo too!) I am sympathetic to many of the arguements presented against creating them in repos, and I do create them for myself on the desktop (so to speak) so I also see the value in that - that said, I almost entirely depend on the repo indices in PocketSword (a most marvellous tool) where I cannot create them, so cannot entirely see myself giving up that mode. I haven't yet spent much time with the And-bible though I down own an Asus ePad. ~A On Wednesday, January 23, 2013, Nic Carter wrote: > > My suggestion would be to avoid pre-built indices. However, given I'm the > one who first went about making them, I think there are pros in certain > situations. :P > > In my situation, I get to be gatekeeper over the entire solution > (PocketSword), where users cannot change the version of clucene or libsword > behind my back. And so I can be aware of when things might break (& > increment my "v1" bit of the download URL of the indices). > > BTW, I would strongly suggest that no one else use either the and-bible or > PocketSword pre-built indices due to incompatibilities that have been > explained in other posts. :) > I'd also strongly suggest that no one else creates new ones for another > platform, unless it's absolutely necessary. They are messy, as you can > probably gather from all these posts! :) > > > Thanks, ybic > nic... :) > > On 24/01/2013, at 5:18 AM, Peter von Kaehne > > wrote: > > > > >> Von: Andrew Thule > > >> There are Pros and Cons either way (resource usage and download time > >> being considerations) as you point out. > > > > There are no pros and only contras. And I certainly have not pointed out > any pros. Nor has DM. Please stop using my name as supposedly in agreement > with you. I find this offensive. > > > > FWIW - If you run a repo for anyone other than yourself with indeces > included, you will create a significant risk of malfunction. For anyone > other than the user of the specific version of libsword and clucene. > > > > As such no one expects from you anything anymore, so, further > explanations are probably pointless. > > > > > > _______________________________________________ > > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From manfred.bergmann at me.com Wed Jan 23 23:25:21 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 07:25:21 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> Message-ID: <8C6586E2-AF1D-4C61-929D-074B41E6EB3B@me.com> Am 23.01.2013 um 23:21 schrieb Jeff Barnes : > > > Sent from my iPhone > > On Jan 23, 2013, at 4:20 PM, Manfred Bergmann wrote: > >> >> Well, you know how Apple is. Much changes, especially over on two major versions. >> Many things have their advantages. Installing Xcode over App Store is pretty much painless (except the download). You get gcc, subversion, git and many other goodies once you've installed it. >> The OS X Java port is now maintained by Oracle which IMO is a good thing as well. >> >> >> Manfred > > I downloaded fink to get gcc. I read all the blogs, etc. that said gcc doesn't come with Xcode anymore. Did I misread something? No need to do that. As Nic pointed out, the command line tools can be installed from Xcode Preferences. And unless you want to compile something from command line directly via issuing gcc you don't need the command line tools to build Xcode projects. Manfred From jbarnesweb at gmail.com Wed Jan 23 11:41:33 2013 From: jbarnesweb at gmail.com (Barnes, Jeffrey) Date: Wed, 23 Jan 2013 13:41:33 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: On Jan 23, 2013, at 12:05:20PM, Manfred Bergmann wrote: > Just out of curiosity, what do you need the objc wrappers for? > Just want to play around with the API. Develop a simple client. Curiosity while I learn to code in Objective-C/Cocoa. Jeff From jbarnesweb at gmail.com Wed Jan 23 13:54:32 2013 From: jbarnesweb at gmail.com (Barnes, Jeffrey) Date: Wed, 23 Jan 2013 15:54:32 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann wrote: > > OK. Can you upgrade to Lion at least? > That would probably be the easiest because the this Xcode project is maintained. > Last night, while we were asleep, my wife poked me in the eye when she rolled over. I upgraded to Mountain Lion today. I must say, the poke in the eye was less painful. It only lasted a few minutes. Gcc? gone Java? gone XCode? gone Subversion client? gone XWindows? Well, you get the idea. But now, I've got the new Xcode and I'm building ObjCSword. So far it's been about 15 minutes? (Not counting the 2 hour download / install / fix of Mountain Lion) More to follow. Jeff From jbarnesweb at gmail.com Wed Jan 23 15:21:07 2013 From: jbarnesweb at gmail.com (Jeff Barnes) Date: Wed, 23 Jan 2013 17:21:07 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> Sent from my iPhone On Jan 23, 2013, at 4:20 PM, Manfred Bergmann wrote: > > Well, you know how Apple is. Much changes, especially over on two major versions. > Many things have their advantages. Installing Xcode over App Store is pretty much painless (except the download). You get gcc, subversion, git and many other goodies once you've installed it. > The OS X Java port is now maintained by Oracle which IMO is a good thing as well. > > > Manfred I downloaded fink to get gcc. I read all the blogs, etc. that said gcc doesn't come with Xcode anymore. Did I misread something? From trevor.jenkins at suneidesis.com Thu Jan 24 03:29:34 2013 From: trevor.jenkins at suneidesis.com (Trevor Jenkins) Date: Thu, 24 Jan 2013 10:29:34 +0000 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> Message-ID: On 23 Jan 2013, at 22:21, Jeff Barnes wrote: > I downloaded fink to get gcc. I read all the blogs, etc. that said gcc doesn't come with Xcode anymore. Did I misread something? The gcc compiler is no longer shipped with Xcode. Instead it comes with the LLVM project's reworking of it. http://llvm.org/ and https://developer.apple.com/library/mac/#documentation/CompilerTools/Conceptual/LLVMCompilerOverview/_index.html The claim is that LLVM produces better object code than its gcc equivalent. The Xcode "command line tools" options will expose the installed compiler and linker for use outside of Xcode, e.g. for hacking with eclipse. Regards, Trevor. <>< Re: deemed! From dfhmch at googlemail.com Thu Jan 24 05:36:12 2013 From: dfhmch at googlemail.com (David Haslam) Date: Thu, 24 Jan 2013 04:36:12 -0800 (PST) Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> Message-ID: <1359030972248-4651788.post@n4.nabble.com> *And Bible* allows the user to create the search index for a module if it does not already exist. This is useful in these situations: (a) The user is currently not [reliably] connected to the Internet, (b) Martin has not yet made the downloadable index for new/updated modules. And Bible does not have a UI option to remove a search index, though this could be done manually by means of the file system, assuming you know where to look within the Android directory structure. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html Sent from the SWORD Dev mailing list archive at Nabble.com. From mjdenham at gmail.com Thu Jan 24 06:10:31 2013 From: mjdenham at gmail.com (Martin Denham) Date: Thu, 24 Jan 2013 13:10:31 +0000 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: <1359030972248-4651788.post@n4.nabble.com> References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> <1359030972248-4651788.post@n4.nabble.com> Message-ID: Hi David, To delete an index in And Bible you long-press the desired module in the Documents list to reveal module and index delete actions in the context menu. Martin On 24 January 2013 12:36, David Haslam wrote: > *And Bible* allows the user to create the search index for a module if it > does not already exist. > > This is useful in these situations: > > (a) The user is currently not [reliably] connected to the Internet, > (b) Martin has not yet made the downloadable index for new/updated modules. > > And Bible does not have a UI option to remove a search index, > though this could be done manually by means of the file system, > assuming you know where to look within the Android directory structure. > > David > > > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbarnesweb at yahoo.com Thu Jan 24 07:17:04 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Thu, 24 Jan 2013 06:17:04 -0800 (PST) Subject: [sword-devel] bindings/objc build broken In-Reply-To: <8C6586E2-AF1D-4C61-929D-074B41E6EB3B@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <65AD65AC-3851-4F0F-9221-6707AA379FA3@gmail.com> <8C6586E2-AF1D-4C61-929D-074B41E6EB3B@me.com> Message-ID: <1359037024.42903.YahooMailNeo@web160705.mail.bf1.yahoo.com> ----- Original Message ----- > From: Manfred Bergmann > To: Jeff Barnes > Cc: SWORD Developers' Collaboration Forum > Sent: Thursday, January 24, 2013 1:25 AM > Subject: Re: [sword-devel] bindings/objc build broken >> I downloaded fink to get gcc. I read all the blogs, etc. that said gcc > doesn't come with Xcode anymore. Did I misread something? > > No need to do that. As Nic pointed out, the command line tools can be installed > from Xcode Preferences. > And unless you want to compile something from command line directly via issuing > gcc you don't need the command line tools to build Xcode projects. > > > Manfred I need gcc for "the rest of the world ex-mac." Not sure, but I think I need gcc to compile the Sword project trunk tip. No? From jbarnesweb at yahoo.com Thu Jan 24 07:52:37 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Thu, 24 Jan 2013 09:52:37 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: On Jan 23, 2013, at 3:54:32PM, "Barnes, Jeffrey" wrote: > > On Jan 23, 2013, at 2:21:09PM, Manfred Bergmann wrote: > >> >> OK. Can you upgrade to Lion at least? >> That would probably be the easiest because the this Xcode project is maintained. >> > > Last night, while we were asleep, my wife poked me in the eye when she rolled over. I upgraded to Mountain Lion today. I must say, the poke in the eye was less painful. It only lasted a few minutes. > > Gcc? gone > Java? gone > XCode? gone > Subversion client? gone > XWindows? > > Well, you get the idea. But now, I've got the new Xcode and I'm building ObjCSword. So far it's been about 15 minutes? (Not counting the 2 hour download / install / fix of Mountain Lion) > > More to follow. > Jeff > I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. Now it fails on the AnalysisHeader step. Here's the last line of the build output. clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' clang: error: no input files Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 Regards, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Thu Jan 24 07:55:10 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 24 Jan 2013 08:55:10 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> Message-ID: On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan wrote: > Hi Greg, > > On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings wrote: > >> >> >> >> SWIG bindings now up-to-date. >> >> Bindings users, please holler if I removed things overzealously. >> >> I haven't tried it, but I believe that this will break BPBible for > example. > > As the bindings are part of SWORD, I believe it makes sense to mirror the > deprecations in the bindings somehow if possible, rather than ignoring the > deprecated definitions. > I know that's what e.g. wxPython does, but I'm not sure how it does it. > I can't see any way of marking the methods as deprecated using SWIG. A Google search has turned up no such evidence that it is even possible. While I would like to mark them as deprecated, I think it is more proper for there to be no such warnings coming from building the engine. I think it would just smack as an issue with building if the engine produced warnings that it uses its own deprecation warnings! > > Doing this will make it easier to support both SWORD 1.6 and SVN, which I > think is desirable until a couple of versions down the road. > Supporting both is not something that either BibleTime or Xiphos is able to do at this point, either. In BT we maintain a separate branch for compatibility with SWORD while in Xiphos we simply can't make a new release until the engine releases. BPBible will probably need to take a similar path. Part of cleaning up warnings from building are to allow the bindings to make it into distros. I've cleaned them up enough since 1.6.2 that hopefully this release will see at least Dmitrijs and whoever is our Fedora maintainer at this point able to build the bindings and include them in the distro which ought to allow BPBible to be packaged as well. Previously at least Debian was choking on the bindings failing to build due to warnings and -Werror flags. In short, I'd rather keep these out unless there's a way to suppress the compile warnings and mark them as deprecated in the SWIG output. If you find evidence of that possibility, please let me know. --Greg > > God Bless, > Ben > ------------------------------------------------------------- > For I have no pleasure in the death of anyone, > declares the Lord God; so turn, and live.? > Ezekiel 18:32 (ESV) > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbarnesweb at yahoo.com Thu Jan 24 07:59:21 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Thu, 24 Jan 2013 09:59:21 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey" wrote: > > I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. > > I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. > > Now it fails on the AnalysisHeader step. Here's the last line of the build output. > > clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' > clang: error: no input files > Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 > > Regards, > Jeff Also, there are compiler warnings on almost every file. The most common one being like the following: /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion loses integer precision: 'unsigned long' to 'unsigned int' etc. I have a gut wrench every time I see a compiler warning. I have to maintain code at work and one of the first things my boss told me to do was clean up the compiler warnings. I have to encourage the other members of my team constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me no like compiler warnings!" -------------- next part -------------- An HTML attachment was scrubbed... URL: From refdoc at gmx.net Thu Jan 24 08:17:06 2013 From: refdoc at gmx.net (=?utf-8?B?cmVmZG9jQGdteC5uZXQ=?=) Date: Thu, 24 Jan 2013 16:17:06 +0100 Subject: [sword-devel] =?utf-8?q?Method_Name_Normalization?= Message-ID: FWIW, I am probably the only frequent Perl binding user and I would accept whatever is easiest for you. Thanks for doing this. Once the bindings are working, I will fix all scripts depending on it Peter Sent from my HTC ----- Reply message ----- From: "Greg Hellings" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] Method Name Normalization Date: Thu, Jan 24, 2013 15:55 On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan wrote: Hi Greg, On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings wrote: SWIG bindings now up-to-date. Bindings users, please holler if I removed things overzealously. I haven't tried it, but I believe that this will break BPBible for example. As the bindings are part of SWORD, I believe it makes sense to mirror the deprecations in the bindings somehow if possible, rather than ignoring the deprecated definitions. I know that's what e.g. wxPython does, but I'm not sure how it does it. I can't see any way of marking the methods as deprecated using SWIG. A Google search has turned up no such evidence that it is even possible. While I would like to mark them as deprecated, I think it is more proper for there to be no such warnings coming from building the engine. I think it would just smack as an issue with building if the engine produced warnings that it uses its own deprecation warnings! ? ? Doing this will make it easier to support both SWORD 1..6 and SVN, which I think is desirable until a couple of versions down the road. Supporting both is not something that either BibleTime or Xiphos is able to do at this point, either. In BT we maintain a separate branch for compatibility with SWORD while in Xiphos we simply can't make a new release until the engine releases. BPBible will probably need to take a similar path. Part of cleaning up warnings from building are to allow the bindings to make it into distros. I've cleaned them up enough since 1.6.2 that hopefully this release will see at least Dmitrijs and whoever is our Fedora maintainer at this point able to build the bindings and include them in the distro which ought to allow BPBible to be packaged as well. Previously at least Debian was choking on the bindings failing to build due to warnings and -Werror flags. In short, I'd rather keep these out unless there's a way to suppress the compile warnings and mark them as deprecated in the SWIG output. If you find evidence of that possibility, please let me know. --Greg?God Bless, Ben ------------------------------------------------------------- For I have no pleasure in the death of anyone, declares the Lord God; so turn, and live.? Ezekiel 18:32 (ESV) _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Thu Jan 24 08:28:53 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 24 Jan 2013 09:28:53 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: Message-ID: On Thu, Jan 24, 2013 at 9:17 AM, refdoc at gmx.net wrote: > > FWIW, I am probably the only frequent Perl binding user and I would accept > whatever is easiest for you. Thanks for doing this. Once the bindings are > working, I will fix all scripts depending on it > Perl and Python bindings should be identical to within the limits of SWIG to emulate them. I have already submitted the chance that removes all deprecated methods from the SWIG bindings. If you do an SVN up, you should get the updated bindings. To help with your updating, you can find the list of deprecated and removed functions in bindings/swig/deprecated.i or similar. --Greg > > Peter > Sent from my HTC > > > ----- Reply message ----- > From: "Greg Hellings" > To: "SWORD Developers' Collaboration Forum" > Subject: [sword-devel] Method Name Normalization > Date: Thu, Jan 24, 2013 15:55 > > > > > > On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan wrote: > >> Hi Greg, >> >> On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings wrote: >> >>> >>> >>> >>> SWIG bindings now up-to-date. >>> >>> Bindings users, please holler if I removed things overzealously. >>> >>> I haven't tried it, but I believe that this will break BPBible for >> example. >> >> As the bindings are part of SWORD, I believe it makes sense to mirror the >> deprecations in the bindings somehow if possible, rather than ignoring the >> deprecated definitions. >> I know that's what e.g. wxPython does, but I'm not sure how it does it. >> > > I can't see any way of marking the methods as deprecated using SWIG. A > Google search has turned up no such evidence that it is even possible. > While I would like to mark them as deprecated, I think it is more proper > for there to be no such warnings coming from building the engine. I think > it would just smack as an issue with building if the engine produced > warnings that it uses its own deprecation warnings! > > >> >> Doing this will make it easier to support both SWORD 1..6 and SVN, which >> I think is desirable until a couple of versions down the road. >> > > Supporting both is not something that either BibleTime or Xiphos is able > to do at this point, either. In BT we maintain a separate branch for > compatibility with SWORD while in Xiphos we simply can't make a new release > until the engine releases. BPBible will probably need to take a similar > path. > > Part of cleaning up warnings from building are to allow the bindings to > make it into distros. I've cleaned them up enough since 1.6.2 that > hopefully this release will see at least Dmitrijs and whoever is our Fedora > maintainer at this point able to build the bindings and include them in the > distro which ought to allow BPBible to be packaged as well. Previously at > least Debian was choking on the bindings failing to build due to warnings > and -Werror flags. > > In short, I'd rather keep these out unless there's a way to suppress the > compile warnings and mark them as deprecated in the SWIG output. If you > find evidence of that possibility, please let me know. > > --Greg > > >> >> God Bless, >> Ben >> ------------------------------------------------------------- >> For I have no pleasure in the death of anyone, >> declares the Lord God; so turn, and live.? >> Ezekiel 18:32 (ESV) >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Thu Jan 24 09:54:23 2013 From: dfhmch at googlemail.com (David Haslam) Date: Thu, 24 Jan 2013 08:54:23 -0800 (PST) Subject: [sword-devel] Pre-verse div and headings In-Reply-To: <1358799197066-4651743.post@n4.nabble.com> References: <4E1C78D8-0178-4A83-9942-7D04EBFFC04F@crosswire.org> <20130121142308.208110@gmx.net> <50FD59B7.5020907@crosswire.org> <5569F54E-5E7C-4AB6-AF81-041AC348FD52@crosswire.org> <50FD804D.7000304@crosswire.org> <1358799197066-4651743.post@n4.nabble.com> Message-ID: <1359046463267-4651796.post@n4.nabble.com> Another reminder for potential newcomers: Pasted from http://crosswire.org/wiki/DevTools:conf_Files#Optional_elements_to_support_particular_features For the GlobalOptionFilter=*OSISHeadings* the accompanying explanation is "(For OSIS texts having non-canonical headings)" David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Pre-verse-div-and-headings-tp4651710p4651796.html Sent from the SWORD Dev mailing list archive at Nabble.com. From manfred.bergmann at me.com Thu Jan 24 10:18:18 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 18:18:18 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> Message-ID: <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> Indeed, there are a lot of warnings, not mentioning CLucene. I'll do a clean checkout of the sources and see if I can replicate your errors. You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. Manfred Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" : > > On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey" wrote: > >> >> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. >> >> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. >> >> Now it fails on the AnalysisHeader step. Here's the last line of the build output. >> >> clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' >> clang: error: no input files >> Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 >> >> Regards, >> Jeff > > Also, there are compiler warnings on almost every file. The most common one being like the following: > > /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion loses integer precision: 'unsigned long' to 'unsigned int' > > etc. > > I have a gut wrench every time I see a compiler warning. I have to maintain code at work and one of the first things my boss told me to do was clean up the compiler warnings. I have to encourage the other members of my team constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me no like compiler warnings!" > From jbarnesweb at yahoo.com Thu Jan 24 12:02:29 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Thu, 24 Jan 2013 14:02:29 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> Message-ID: <9C9BC33C-7422-4951-8153-C6372D891EDC@yahoo.com> On Jan 24, 2013, at 12:18:18PM, Manfred Bergmann wrote: > I'll do a clean checkout of the sources and see if I can replicate your errors. > You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. How do I link against ICU? Are the .h/.cpp files in trunk? Sorry for the need to hold my hand. Jeff From manfred.bergmann at me.com Thu Jan 24 12:27:58 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 20:27:58 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> Message-ID: Alright. Here is what you need to do. in "objc" folder go to "dependencies" and execute "retrieve.sh". This downloads the icu and clucene sources and headers which are required for the Xcode build. I've done some adaptions to the latest sword src changes. One method was removed which gave an error. And there are now a lot of deprecation warnings which I have to go through. I've also removed two old library search paths from the project which pointed to a folder that doesn't exist. If you update your sources it should build fine now. Manfred Am 24.01.2013 um 18:18 schrieb Manfred Bergmann : > Indeed, there are a lot of warnings, not mentioning CLucene. > > I'll do a clean checkout of the sources and see if I can replicate your errors. > You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. > > > Manfred > > Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" : > >> >> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey" wrote: >> >>> >>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. >>> >>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. >>> >>> Now it fails on the AnalysisHeader step. Here's the last line of the build output. >>> >>> clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' >>> clang: error: no input files >>> Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 >>> >>> Regards, >>> Jeff >> >> Also, there are compiler warnings on almost every file. The most common one being like the following: >> >> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion loses integer precision: 'unsigned long' to 'unsigned int' >> >> etc. >> >> I have a gut wrench every time I see a compiler warning. I have to maintain code at work and one of the first things my boss told me to do was clean up the compiler warnings. I have to encourage the other members of my team constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me no like compiler warnings!" >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From manfred.bergmann at me.com Thu Jan 24 13:03:10 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 21:03:10 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <9C9BC33C-7422-4951-8153-C6372D891EDC@yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> <9C9BC33C-7422-4951-8153-C6372D891EDC@yahoo.com> Message-ID: Am 24.01.2013 um 20:02 schrieb "Barnes, Jeffrey" : > > On Jan 24, 2013, at 12:18:18PM, Manfred Bergmann wrote: > >> I'll do a clean checkout of the sources and see if I can replicate your errors. >> You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. > > How do I link against ICU? Are the .h/.cpp files in trunk? The project links against libicu-core which is shipped with OS X. The ICU headers are in the dependencies once "retrieve.sh" is executed. Manfred From jbarnesweb at yahoo.com Thu Jan 24 13:06:28 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Thu, 24 Jan 2013 15:06:28 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> Message-ID: <0950AE58-34D3-4A3C-B4FF-4F72DB2FD4A6@yahoo.com> I had trouble updating, so I blew away my local trunk directory. I tried the command line. PACCPL-334LAGYA:sword jbarne200$ svn co https://crosswire.org/svn/sword/trunk Error validating server certificate for 'https://crosswire.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! - The certificate hostname does not match. Certificate information: - Hostname: www.crosswire.org - Valid: from Fri, 04 May 2012 23:03:07 GMT until Sat, 04 May 2013 23:03:07 GMT - Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, -- - Fingerprint: 60:d4:77:54:37:d3:37:ed:42:92:7b:eb:1a:f0:25:f7:50:ff:c2:57 (R)eject, accept (t)emporarily or accept (p)ermanently? p svn: PROPFIND of '/svn/sword/trunk': SSL handshake failed: Secure connection truncated (https://crosswire.org) I tried from Xcode. It told me to validate the fingerprint (where do I do that?). Is the repository down? I thought the command line version should have worked. Jeff On Jan 24, 2013, at 2:27:58PM, Manfred Bergmann wrote: > Alright. > Here is what you need to do. > in "objc" folder go to "dependencies" and execute "retrieve.sh". > This downloads the icu and clucene sources and headers which are required for the Xcode build. > > I've done some adaptions to the latest sword src changes. One method was removed which gave an error. And there are now a lot of deprecation warnings which I have to go through. > I've also removed two old library search paths from the project which pointed to a folder that doesn't exist. > > If you update your sources it should build fine now. > > > > Manfred > > Am 24.01.2013 um 18:18 schrieb Manfred Bergmann : > >> Indeed, there are a lot of warnings, not mentioning CLucene. >> >> I'll do a clean checkout of the sources and see if I can replicate your errors. >> You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. >> >> >> Manfred >> >> Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" : >> >>> >>> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey" wrote: >>> >>>> >>>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. >>>> >>>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. >>>> >>>> Now it fails on the AnalysisHeader step. Here's the last line of the build output. >>>> >>>> clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' >>>> clang: error: no input files >>>> Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 >>>> >>>> Regards, >>>> Jeff >>> >>> Also, there are compiler warnings on almost every file. The most common one being like the following: >>> >>> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion loses integer precision: 'unsigned long' to 'unsigned int' >>> >>> etc. >>> >>> I have a gut wrench every time I see a compiler warning. I have to maintain code at work and one of the first things my boss told me to do was clean up the compiler warnings. I have to encourage the other members of my team constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me no like compiler warnings!" >>> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > From manfred.bergmann at me.com Thu Jan 24 13:18:10 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 21:18:10 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <0950AE58-34D3-4A3C-B4FF-4F72DB2FD4A6@yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> <0950AE58-34D3-4A3C-B4FF-4F72DB2FD4A6@yahoo.com> Message-ID: <99C0C106-5D0B-4497-B034-DBB71E9C304E@me.com> I'm not sure. Maybe try plain http? It's also enough to rm objc and do svn update. It will fetch objc folder again. Manfred Am 24.01.2013 um 21:06 schrieb "Barnes, Jeffrey" : > I had trouble updating, so I blew away my local trunk directory. > > I tried the command line. > > PACCPL-334LAGYA:sword jbarne200$ svn co https://crosswire.org/svn/sword/trunk > Error validating server certificate for 'https://crosswire.org:443': > - The certificate is not issued by a trusted authority. Use the > fingerprint to validate the certificate manually! > - The certificate hostname does not match. > Certificate information: > - Hostname: www.crosswire.org > - Valid: from Fri, 04 May 2012 23:03:07 GMT until Sat, 04 May 2013 23:03:07 GMT > - Issuer: SomeOrganizationalUnit, SomeOrganization, SomeCity, SomeState, -- > - Fingerprint: 60:d4:77:54:37:d3:37:ed:42:92:7b:eb:1a:f0:25:f7:50:ff:c2:57 > (R)eject, accept (t)emporarily or accept (p)ermanently? p > svn: PROPFIND of '/svn/sword/trunk': SSL handshake failed: Secure connection truncated (https://crosswire.org) > > I tried from Xcode. It told me to validate the fingerprint (where do I do that?). > > Is the repository down? I thought the command line version should have worked. > > Jeff > > On Jan 24, 2013, at 2:27:58PM, Manfred Bergmann wrote: > >> Alright. >> Here is what you need to do. >> in "objc" folder go to "dependencies" and execute "retrieve.sh". >> This downloads the icu and clucene sources and headers which are required for the Xcode build. >> >> I've done some adaptions to the latest sword src changes. One method was removed which gave an error. And there are now a lot of deprecation warnings which I have to go through. >> I've also removed two old library search paths from the project which pointed to a folder that doesn't exist. >> >> If you update your sources it should build fine now. >> >> >> >> Manfred >> >> Am 24.01.2013 um 18:18 schrieb Manfred Bergmann : >> >>> Indeed, there are a lot of warnings, not mentioning CLucene. >>> >>> I'll do a clean checkout of the sources and see if I can replicate your errors. >>> You should however build with ICU. CLucene it not necessarily needed since on Mac the index is built using SearchKit framework. >>> >>> >>> Manfred >>> >>> Am 24.01.2013 um 15:59 schrieb "Barnes, Jeffrey" : >>> >>>> >>>> On Jan 24, 2013, at 9:52:37AM, "Barnes, Jeffrey" wrote: >>>> >>>>> >>>>> I'm having some difficulty with the build with Mountain Lion, Xcode 4.5.2. >>>>> >>>>> I double-clicked the ObjCSword.xcodeproj file to open it in Xcode. I ran the build. It failed on Lucene dependency. Just to try to get it to build, I removed the lucene define and ran the build again. It failed on the ICU dependency. I removed the ICU define. >>>>> >>>>> Now it fails on the AnalysisHeader step. Here's the last line of the build output. >>>>> >>>>> clang: error: no such file or directory: '/Users/jbarne200/sword/trunk/bindings/objc/dependencies/clucene/CLucene/analysis/AnalysisHeader.cpp' >>>>> clang: error: no input files >>>>> Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1 >>>>> >>>>> Regards, >>>>> Jeff >>>> >>>> Also, there are compiler warnings on almost every file. The most common one being like the following: >>>> >>>> /Users/jbarne200/sword/trunk/include/stringmgr.h:111:31: Implicit conversion loses integer precision: 'unsigned long' to 'unsigned int' >>>> >>>> etc. >>>> >>>> I have a gut wrench every time I see a compiler warning. I have to maintain code at work and one of the first things my boss told me to do was clean up the compiler warnings. I have to encourage the other members of my team constantly to keep trunk pristine. Forgive me if I'm being pedantic, but "Me no like compiler warnings!" >>>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> > From jbarnesweb at yahoo.com Thu Jan 24 14:04:18 2013 From: jbarnesweb at yahoo.com (Barnes, Jeffrey) Date: Thu, 24 Jan 2013 16:04:18 -0500 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <99C0C106-5D0B-4497-B034-DBB71E9C304E@me.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> <0950AE58-34D3-4A3C-B4FF-4F72DB2FD4A6@yahoo.com> <99C0C106-5D0B-4497-B034-DBB71E9C304E@me.com> Message-ID: <40A4F5BF-46BD-4D7D-98CE-BEC94815B5C1@yahoo.com> Ok, everything built. (Hooray!) I recommend updating bindings/objc/README to the following. Building ObjCSword wrapper framework howto ========================================== Mac OS X target: This project can only be built on OS X 10.8 (Mountain Lion) or later. To build for Mac OS X: 1) Change to the dependencies directory. 2) Run retrieve.sh. This downloads the icu and clucene sources and headers which are required for the Xcode build. To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. This opens Xcode and loads the Sword Project. Press + B to build (or select Build from the Product menu). To build from the command line, enter xcodebuild -project ./ObjCSword.xcodeproj. +++++++++++++ How can I reference this new ObjCSword in another project? Thanks so much for your help Manfred. Jeff From manfred.bergmann at me.com Thu Jan 24 14:11:15 2013 From: manfred.bergmann at me.com (Manfred Bergmann) Date: Thu, 24 Jan 2013 22:11:15 +0100 Subject: [sword-devel] bindings/objc build broken In-Reply-To: <40A4F5BF-46BD-4D7D-98CE-BEC94815B5C1@yahoo.com> References: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> <1358948325.40737.YahooMailNeo@web160703.mail.bf1.yahoo.com> <1358951478.35413.YahooMailNeo@web160706.mail.bf1.yahoo.com> <7AED7654-C9BC-4F9D-8CFE-E23191840901@me.com> <1358953788.13550.YahooMailNeo@web160705.mail.bf1.yahoo.com> <633D15D8-1C90-4AFC-8C47-B6E7D1E0956D@me.com> <1358954660.64301.YahooMailNeo@web160702.mail.bf1.yahoo.com> <239949E4-CB51-4E0E-A69E-656FA378AFAC@me.com> <0950AE58-34D3-4A3C-B4FF-4F72DB2FD4A6@yahoo.com> <99C0C106-5D0B-4497-B034-DBB71E9C304E@me.com> <40A4F5BF-46BD-4D7D-98CE-BEC94815B5C1@yahoo.com> Message-ID: <8B53D52A-4A50-46A4-AA25-95557A2DF38C@me.com> Yep, thanks. I will update the README. You can now use the result (ObjCSword.framework) as a dependency in another project. Or you add the whole Xcode project to another Xcode project. If you build the outer project the inner project is built as well or actually the inner one is built first. You can also have a look at the (too few) OCUnit tests (i.e. SwordModuleTest) in ObjCSword, at least regarding the API usage. Manfred Am 24.01.2013 um 22:04 schrieb "Barnes, Jeffrey" : > Ok, everything built. (Hooray!) > > I recommend updating bindings/objc/README to the following. > > Building ObjCSword wrapper framework howto > ========================================== > > Mac OS X target: > This project can only be built on OS X 10.8 (Mountain Lion) or later. > > To build for Mac OS X: > > 1) Change to the dependencies directory. > 2) Run retrieve.sh. This downloads the icu and clucene sources and headers which are required for the Xcode build. > > To build from inside Xcode double-click the ObjCSword.xcodeproj in Finder. This opens Xcode and loads the Sword Project. Press + B to build (or select Build from the Product menu). > > To build from the command line, enter xcodebuild -project ./ObjCSword.xcodeproj. > > > +++++++++++++ > > How can I reference this new ObjCSword in another project? > > Thanks so much for your help Manfred. > > Jeff > > From trampster at gmail.com Thu Jan 24 16:38:18 2013 From: trampster at gmail.com (Daniel Hughes) Date: Fri, 25 Jan 2013 12:38:18 +1300 Subject: [sword-devel] Location of prebuilt lucene indexes. In-Reply-To: References: <20130123160231.213410@gmx.net> <20130123181807.85590@gmx.net> <58B95878-0277-4A35-A9C5-AE9559BCCE06@mac.com> <1359030972248-4651788.post@n4.nabble.com> Message-ID: Thanks all for your replies. I am using Lucene.net which is a .net port of the java Lucene. I have been able to consume an index created by xiphos which I assume uses clucene. However based on the replies here I think I will generate my own indexes to avoid and compatibility issues. Daniel Hughes On Fri, Jan 25, 2013 at 2:10 AM, Martin Denham wrote: > Hi David, > > To delete an index in And Bible you long-press the desired module in the > Documents list to reveal module and index delete actions in the context > menu. > > Martin > > On 24 January 2013 12:36, David Haslam wrote: > >> *And Bible* allows the user to create the search index for a module if it >> does not already exist. >> >> This is useful in these situations: >> >> (a) The user is currently not [reliably] connected to the Internet, >> (b) Martin has not yet made the downloadable index for new/updated >> modules. >> >> And Bible does not have a UI option to remove a search index, >> though this could be done manually by means of the file system, >> assuming you know where to look within the Android directory structure. >> >> David >> >> >> >> >> >> -- >> View this message in context: >> http://sword-dev.350566.n4.nabble.com/Location-of-prebuilt-lucene-indexes-tp4651756p4651788.html >> Sent from the SWORD Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 24 19:29:14 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 24 Jan 2013 21:29:14 -0500 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) Message-ID: Has something changed in the Xiphos build? I've had no problems until 4411 (last successful build before was 4408). The build starts off ok: [ 42/130] cxx: src/backend/module_manager.cc -> build/default/src/backend/module_manager_1.o [ 43/130] cxx: src/backend/sword_main.cc -> build/default/src/backend/sword_main_1.o ../src/backend/module_manager.cc: In function ?MOD_MGR* backend_module_mgr_get_next_module()?: ../src/backend/module_manager.cc:171:30: warning: ?const char* sword::SWModule::Name() const? is deprecated (declared at /usr/local/include/sword/swmodule.h:285) [-Wdeprecated-declarations] ../src/backend/module_manager.cc:171:30: error: invalid conversion from ?const char*? to ?gchar* {aka char*}? [-fpermissive] ../src/backend/module_manager.cc:176:43: warning: ?const char* sword::SWModule::Lang(char*)? is deprecated (declared at /usr/local/include/sword/swmodule.h:353) [-Wdeprecated-declarations] ../src/backend/module_manager.cc:177:43: warning: ?const char* sword::SWModule::Type() const? is deprecated (declared at /usr/local/include/sword/swmodule.h:313) [-Wdeprecated-declarations] ../src/backend/module_manager.cc:216:48: warning: ?const char* sword::SWModule::Description() const? is deprecated (declared at /usr/local/include/sword/swmodule.h:299) [-Wdeprecated-declarations] ../src/backend/module_manager.cc:216:48: error: invalid conversion from ?const char*? to ?char*? [-fpermissive] But ends with: ../src/backend/sword_main.cc: In member function ?const char* BackEnd::get_next_listkey()?: ../src/backend/sword_main.cc:921:24: warning: ?char sword::SWKey::Error()? is deprecated (declared at /usr/local/include/sword/swkey.h:159) [-Wdeprecated-declarations] ../src/backend/sword_main.cc: In member function ?int BackEnd::set_range(char*)?: ../src/backend/sword_main.cc:943:57: warning: ?sword::ListKey sword::VerseKey::ParseVerseList(const char*, const char*, bool, bool)? is deprecated (declared at /usr/local/include/sword/versekey.h:452) [-Wdeprecated-declarations] Waf: Leaving directory `/usr/local/src/xiphos/build' Build failed: -> task failed (err #1): {task: cxx module_manager.cc -> module_manager_1.o} -> task failed (err #1): {task: cxx sword_main.cc -> sword_main_1.o} Is anyone else having trouble? I haven't changed my environment (since revision 4408) Can anyone tell from the above what the issue might be? ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From karl at kleinpaste.org Thu Jan 24 19:34:17 2013 From: karl at kleinpaste.org (Karl Kleinpaste) Date: Thu, 24 Jan 2013 21:34:17 -0500 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: (Andrew Thule's message of "Thu, 24 Jan 2013 21:29:14 -0500") References: Message-ID: If you're trying to build Xiphos against recently updated Sword, it's going to be a mess right now. I'll deal with it by week's end. From thulester at gmail.com Thu Jan 24 20:39:32 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 24 Jan 2013 22:39:32 -0500 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: References: Message-ID: I was Karl. Thanks for the heads up. I look forward to your fixes (no rush). ~A On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote: > If you're trying to build Xiphos against recently updated Sword, it's > going to be a mess right now. I'll deal with it by week's end. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 24 20:41:05 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 24 Jan 2013 22:41:05 -0500 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: References: Message-ID: .. and thinking about it, you're correct. Something had changed on my end, namely the Sword revision I was running. I had forgotten about that, until you pointed it out. ~A On Thu, Jan 24, 2013 at 10:39 PM, Andrew Thule wrote: > I was Karl. Thanks for the heads up. I look forward to your fixes (no > rush). > > ~A > > > On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote: > >> If you're trying to build Xiphos against recently updated Sword, it's >> going to be a mess right now. I'll deal with it by week's end. >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Thu Jan 24 20:42:56 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 24 Jan 2013 21:42:56 -0600 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: References: Message-ID: If you monitored the proper message stream you'd see I have created a patch which attempts to fix this compile problem but introduces a minor display bug in the process (module text will not display at all...). --Greg On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule wrote: > I was Karl. Thanks for the heads up. I look forward to your fixes (no > rush). > > ~A > > > On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote: > >> If you're trying to build Xiphos against recently updated Sword, it's >> going to be a mess right now. I'll deal with it by week's end. >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 24 21:00:25 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 24 Jan 2013 23:00:25 -0500 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: References: Message-ID: Thanks Greg .. Ill go looking for the patch .. or perhaps I won't. Ill give it thought. It might be best if I keep a working version of Xiphos, allowing for the compiler problems, until Karl's updates are merged. I'm not sure how bad Xiphos withdraw can get .. ~A On Thu, Jan 24, 2013 at 10:42 PM, Greg Hellings wrote: > If you monitored the proper message stream you'd see I have created a > patch which attempts to fix this compile problem but introduces a minor > display bug in the process (module text will not display at all...). > > --Greg > > > On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule wrote: > >> I was Karl. Thanks for the heads up. I look forward to your fixes (no >> rush). >> >> ~A >> >> >> On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote: >> >>> If you're trying to build Xiphos against recently updated Sword, it's >>> going to be a mess right now. I'll deal with it by week's end. >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Thu Jan 24 21:20:46 2013 From: thulester at gmail.com (Andrew Thule) Date: Thu, 24 Jan 2013 23:20:46 -0500 Subject: [sword-devel] Question about CMAKE build proceedures Message-ID: I'm still fairly new to using CMAKE (but liking it). I'm finally starting to feel comfortable with its use, but still have questions .. so if this is a newbie question, sorry. Using traditional "./configure; make; make install' I could simply grab a more recent copy (of sword) via svn and make && make install. However, I'm finding with CMAKE I have to completely blow away my cmake build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword". If I don't, I seem to get never ending compiler/build loops. Is it generally necessary to start with a fresh cmake build directory before make && make install? ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Thu Jan 24 21:26:56 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 24 Jan 2013 22:26:56 -0600 Subject: [sword-devel] Question about CMAKE build proceedures In-Reply-To: References: Message-ID: I have found it usually necessary. It is heavily encouraged in CMake, and enforced in SWORD's scripts for just that reason, to do a build from outside of the main source directory in an entirely enclosed environment. To be truthful, when building with the autofoo toolchain I usually found the same difficulty and got in the habit of building that from a subdirectory as well. In general, you shouldn't need to blow away the directory and start again unless the CMake files have changed or you want to use different options in the build process. As the maintainer of the CMake toolchain, I find myself doing it frequently, but most of the time it shouldn't be necessary. I have made quite a few changes over the past few months, though, to accommodate a number of enhancements, usually related to the bindings. --Greg On Thu, Jan 24, 2013 at 10:20 PM, Andrew Thule wrote: > I'm still fairly new to using CMAKE (but liking it). I'm finally starting > to feel comfortable with its use, but still have questions .. so if this is > a newbie question, sorry. > > Using traditional "./configure; make; make install' I could simply grab a > more recent copy (of sword) via svn and make && make install. > > However, I'm finding with CMAKE I have to completely blow away my cmake > build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword". > If I don't, I seem to get never ending compiler/build loops. > > Is it generally necessary to start with a fresh cmake build directory > before make && make install? > > ~A > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Fri Jan 25 04:42:08 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Fri, 25 Jan 2013 12:42:08 +0100 Subject: [sword-devel] CD ISO Message-ID: <51026F90.4040609@crosswire.org> Dear Frontend Teams, I'm planning to burn CDs for people (about 60) who have requested them (yes, we still get occasional CD requests), and was wondering if you might wish to update your stuff in the 'latest' ISO folder here which is the root from where we build the ISO. ftp://ftp.crosswire.org/pub/sword/iso/latest/ I'll update the modules and clean off the ridiculously archaic blobs of whatever. Historically, we've tried to include installers for Mac, Windows, and Linux. I'm conceding to give up on the Linux software (on the CD), so we should probably just remove all of our Linux binary bundles. These installers should be configured to allow installing of modules from the CD. The InstallMgr class supports installation not just from a remote source, but from a local path as well. If your installers could add the root of the CD path as an install source, that would be excellent. We also try to make things run from the CD if possible. I know BPBible has a 'portable' install for this and some of our other frontends run find from the CD as well. If there is a binary you can place somewhere on the CD that, when double clicked, it can start and find it's modules from the CD (at least), that would be great. SWORD looks in the current folder for modules, so if you place your binary in the root of the CD, it might just magically work. Otherwise, you could have a subdirectory with your stuff and include a sword.conf which specifies a datapath of ../ or something. Just ideas. You can download the latest ISO image from here so you can locally update it and play to test how your stuff works. ftp://ftp.crosswire.org/pub/sword/iso/ When you get it working well, if you could update the crosswire.org:/home/sword/ftp/pub/sword/iso/latest/ with your stuff, that would be great. I'm also happy to update the CD autorun splash screens with anything you'd like. Not sure how this works on a Mac, but we launch a silly little windows app with buttons to launch each installer. We could also think about instructions to help people burn this to a thumb drive. Thanks for any help, Troy From jonmmorgan at gmail.com Fri Jan 25 06:31:16 2013 From: jonmmorgan at gmail.com (Jonathan Morgan) Date: Sat, 26 Jan 2013 00:31:16 +1100 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> Message-ID: Hi Greg, On Fri, Jan 25, 2013 at 1:55 AM, Greg Hellings wrote: > > > > On Sun, Jan 20, 2013 at 5:30 PM, Ben Morgan wrote: > >> Hi Greg, >> >> On Mon, Jan 21, 2013 at 6:28 AM, Greg Hellings wrote: >> >>> >>> >>> >>> SWIG bindings now up-to-date. >>> >>> Bindings users, please holler if I removed things overzealously. >>> >>> I haven't tried it, but I believe that this will break BPBible for >> example. >> >> As the bindings are part of SWORD, I believe it makes sense to mirror the >> deprecations in the bindings somehow if possible, rather than ignoring the >> deprecated definitions. >> I know that's what e.g. wxPython does, but I'm not sure how it does it. >> > > I can't see any way of marking the methods as deprecated using SWIG. A > Google search has turned up no such evidence that it is even possible. > While I would like to mark them as deprecated, I think it is more proper > for there to be no such warnings coming from building the engine. I think > it would just smack as an issue with building if the engine produced > warnings that it uses its own deprecation warnings! > Can you not just make deprecations.i be conditionally included based on some kind of "include deprecated methods" compilation variable? That way it is still user choice, but to me it feels wrong to have methods available in C++ but not bindings. Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: From thulester at gmail.com Fri Jan 25 08:48:05 2013 From: thulester at gmail.com (Andrew Thule) Date: Fri, 25 Jan 2013 10:48:05 -0500 Subject: [sword-devel] Question about CMAKE build proceedures In-Reply-To: References: Message-ID: Thanks Greg. Different tools, different philosophies - so it's nice to understand the thinking behind the tool. One thing to be said for Cmake builds, is the build information is so well presented. ~A On Thursday, January 24, 2013, Greg Hellings wrote: > I have found it usually necessary. It is heavily encouraged in CMake, and > enforced in SWORD's scripts for just that reason, to do a build from > outside of the main source directory in an entirely enclosed environment. > > To be truthful, when building with the autofoo toolchain I usually found > the same difficulty and got in the habit of building that from a > subdirectory as well. > > In general, you shouldn't need to blow away the directory and start again > unless the CMake files have changed or you want to use different options in > the build process. As the maintainer of the CMake toolchain, I find myself > doing it frequently, but most of the time it shouldn't be necessary. I have > made quite a few changes over the past few months, though, to accommodate a > number of enhancements, usually related to the bindings. > > --Greg > > > On Thu, Jan 24, 2013 at 10:20 PM, Andrew Thule > > wrote: > >> I'm still fairly new to using CMAKE (but liking it). I'm finally >> starting to feel comfortable with its use, but still have questions .. so >> if this is a newbie question, sorry. >> >> Using traditional "./configure; make; make install' I could simply grab a >> more recent copy (of sword) via svn and make && make install. >> >> However, I'm finding with CMAKE I have to completely blow away my cmake >> build directory before I "cmake -DSWORD_BINDINGS="Perl Python" ../sword". >> If I don't, I seem to get never ending compiler/build loops. >> >> Is it generally necessary to start with a fresh cmake build directory >> before make && make install? >> >> ~A >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org > 'cvml', 'sword-devel at crosswire.org');> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 25 09:23:23 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 25 Jan 2013 10:23:23 -0600 Subject: [sword-devel] CD ISO In-Reply-To: <51026F90.4040609@crosswire.org> References: <51026F90.4040609@crosswire.org> Message-ID: On Fri, Jan 25, 2013 at 5:42 AM, Troy A. Griffitts wrote: > Dear Frontend Teams, > > I'm planning to burn CDs for people (about 60) who have requested them > (yes, we still get occasional CD requests), and was wondering if you might > wish to update your stuff in the 'latest' ISO folder here which is the root > from where we build the ISO. > > ftp://ftp.crosswire.org/pub/**sword/iso/latest/ > > I'll update the modules and clean off the ridiculously archaic blobs of > whatever. > Is your intention for this CD to include software based off of 1.6.2 or will 1.7 be finished before that for front-ends to target? --Greg > > Historically, we've tried to include installers for Mac, Windows, and > Linux. I'm conceding to give up on the Linux software (on the CD), so we > should probably just remove all of our Linux binary bundles. > > These installers should be configured to allow installing of modules from > the CD. The InstallMgr class supports installation not just from a remote > source, but from a local path as well. If your installers could add the > root of the CD path as an install source, that would be excellent. > > We also try to make things run from the CD if possible. I know BPBible > has a 'portable' install for this and some of our other frontends run find > from the CD as well. If there is a binary you can place somewhere on the > CD that, when double clicked, it can start and find it's modules from the > CD (at least), that would be great. SWORD looks in the current folder for > modules, so if you place your binary in the root of the CD, it might just > magically work. Otherwise, you could have a subdirectory with your stuff > and include a sword.conf which specifies a datapath of ../ or something. > Just ideas. > > You can download the latest ISO image from here so you can locally update > it and play to test how your stuff works. > > ftp://ftp.crosswire.org/pub/**sword/iso/ > > When you get it working well, if you could update the crosswire.org: > /home/sword/ftp/**pub/sword/iso/latest/ with your stuff, that would be > great. I'm also happy to update the CD autorun splash screens with > anything you'd like. Not sure how this works on a Mac, but we launch a > silly little windows app with buttons to launch each installer. > > We could also think about instructions to help people burn this to a thumb > drive. > > Thanks for any help, > > Troy > > > > ______________________________**_________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/**mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Fri Jan 25 09:33:10 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Fri, 25 Jan 2013 17:33:10 +0100 Subject: [sword-devel] CD ISO In-Reply-To: References: <51026F90.4040609@crosswire.org> Message-ID: <5102B3C6.9060606@crosswire.org> I'm building my new stuff against svn head. You can build against whatever you think is stable right now. If you have a working binary, I would just drop it in place right now, and then update it when you have a stable new release. On 01/25/2013 05:23 PM, Greg Hellings wrote: > > > > On Fri, Jan 25, 2013 at 5:42 AM, Troy A. Griffitts > > wrote: > > Dear Frontend Teams, > > I'm planning to burn CDs for people (about 60) who have requested > them (yes, we still get occasional CD requests), and was wondering > if you might wish to update your stuff in the 'latest' ISO folder > here which is the root from where we build the ISO. > > ftp://ftp.crosswire.org/pub/sword/iso/latest/ > > I'll update the modules and clean off the ridiculously archaic > blobs of whatever. > > > Is your intention for this CD to include software based off of 1.6.2 > or will 1.7 be finished before that for front-ends to target? > > --Greg > > > Historically, we've tried to include installers for Mac, Windows, > and Linux. I'm conceding to give up on the Linux software (on the > CD), so we should probably just remove all of our Linux binary > bundles. > > These installers should be configured to allow installing of > modules from the CD. The InstallMgr class supports installation > not just from a remote source, but from a local path as well. If > your installers could add the root of the CD path as an install > source, that would be excellent. > > We also try to make things run from the CD if possible. I know > BPBible has a 'portable' install for this and some of our other > frontends run find from the CD as well. If there is a binary you > can place somewhere on the CD that, when double clicked, it can > start and find it's modules from the CD (at least), that would be > great. SWORD looks in the current folder for modules, so if you > place your binary in the root of the CD, it might just magically > work. Otherwise, you could have a subdirectory with your stuff > and include a sword.conf which specifies a datapath of ../ or > something. Just ideas. > > You can download the latest ISO image from here so you can locally > update it and play to test how your stuff works. > > ftp://ftp.crosswire.org/pub/sword/iso/ > > When you get it working well, if you could update the > crosswire.org:/home/sword/ftp/pub/sword/iso/latest/ with your > stuff, that would be great. I'm also happy to update the CD > autorun splash screens with anything you'd like. Not sure how > this works on a Mac, but we launch a silly little windows app with > buttons to launch each installer. > > We could also think about instructions to help people burn this to > a thumb drive. > > Thanks for any help, > > Troy > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 25 12:44:53 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 25 Jan 2013 13:44:53 -0600 Subject: [sword-devel] Xiphos: Checked out revision 4411. (errors) In-Reply-To: References: Message-ID: On Thu, Jan 24, 2013 at 10:00 PM, Andrew Thule wrote: > Thanks Greg .. Ill go looking for the patch .. or perhaps I won't. Ill > give it thought. > It might be best if I keep a working version of Xiphos, allowing for the > compiler problems, until Karl's updates are merged. > I just pushed an update to r4444 which fixes the newest set of deprecations in SWORD and also fixes the module display issue. You'll need to get the latest SWORD (these deprecations were just in the past day or three) and Xiphos. --Greg > > I'm not sure how bad Xiphos withdraw can get .. > ~A > > > On Thu, Jan 24, 2013 at 10:42 PM, Greg Hellings wrote: > >> If you monitored the proper message stream you'd see I have created a >> patch which attempts to fix this compile problem but introduces a minor >> display bug in the process (module text will not display at all...). >> >> --Greg >> >> >> On Thu, Jan 24, 2013 at 9:39 PM, Andrew Thule wrote: >> >>> I was Karl. Thanks for the heads up. I look forward to your fixes (no >>> rush). >>> >>> ~A >>> >>> >>> On Thu, Jan 24, 2013 at 9:34 PM, Karl Kleinpaste wrote: >>> >>>> If you're trying to build Xiphos against recently updated Sword, it's >>>> going to be a mess right now. I'll deal with it by week's end. >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel at crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel at crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at gmail.com Fri Jan 25 12:47:30 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Fri, 25 Jan 2013 13:47:30 -0600 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> Message-ID: On Sun, Jan 20, 2013 at 3:02 PM, Greg Hellings wrote: > > > Additionally, BibleTime's sword-svn-compat branch has been updated to > build cleanly against this, (excluding the unused variables message I > mentioned in the other thread). > > --Greg > On the heels of the second set of deprecations, Xiphos now works again and you can fetch r4444 or beyond from the repository to solve compatibility with the new naming scheme. Updating Xiphos is more important than updating BibleTime as the changes caused Xiphos' build to fail compiling and later to produce blank module text, both of which r4444 and the latest SWORD fix. BT's fixes only eliminate warnings. --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From yudahsshadow at gmx.com Fri Jan 25 14:53:15 2013 From: yudahsshadow at gmx.com (David Blue) Date: Fri, 25 Jan 2013 16:53:15 -0500 Subject: [sword-devel] Trends in mobile platforms In-Reply-To: <1358766665083-4651723.post@n4.nabble.com> References: <1358107307823-4651673.post@n4.nabble.com> <1358766665083-4651723.post@n4.nabble.com> Message-ID: <96bcd922-4f70-4669-8062-0470d8c1be98@email.android.com> FWIW QML is also used as a scripting language for KDE's plasma workspace, so supporting pray be worth our while to allow plasmoids to be developed that support sword -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan-husmann at t-online.de Sat Jan 26 01:46:00 2013 From: stefan-husmann at t-online.de (Stefan Husmann) Date: Sat, 26 Jan 2013 09:46:00 +0100 Subject: [sword-devel] Method Name Normalization In-Reply-To: References: <50FAC626.3000304@crosswire.org> Message-ID: <510397C8.30202@t-online.de> Am 25.01.2013 20:47, schrieb Greg Hellings: > On Sun, Jan 20, 2013 at 3:02 PM, Greg Hellings wrote: >> >> >> Additionally, BibleTime's sword-svn-compat branch has been updated to >> build cleanly against this, (excluding the unused variables message I >> mentioned in the other thread). >> >> --Greg >> > > On the heels of the second set of deprecations, Xiphos now works again and > you can fetch r4444 or beyond from the repository to solve compatibility > with the new naming scheme. Updating Xiphos is more important than updating > BibleTime as the changes caused Xiphos' build to fail compiling and later > to produce blank module text, both of which r4444 and the latest SWORD fix. > BT's fixes only eliminate warnings. > > --Greg > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > Thanks, you can close bug #497 also. Best Regards From christopherbr7 at hotmail.com Fri Jan 25 16:09:40 2013 From: christopherbr7 at hotmail.com (christopher brown) Date: Fri, 25 Jan 2013 18:09:40 -0500 Subject: [sword-devel] Hello, I need help with the Sword Utilities Message-ID: I have been trying to run the sword utilities for about a week now. i have tried to find information on the exact line to use in the command prompt i am running windows xp sp3, osis2mod wont run from the folder it is in, i have to run it from cmd. When i run it from the folder it appears breifly and dissappears, so i have to drag the exe to the command prompt, i dont know if this is normal. if someone could paste an example of what string to use to make a module that would be great. Here is some of what i have tried through the prompt C:\Documents and Settings\All Users\Application Data\Sword>echo off ------------------------------------------ addld: Lexicon and Dictionary creation tool diatheke: multi-purpose command-line frontend imp2gbs: General Book creation tool imp2ld: Lexicon and Dictionary creation tool imp2vs: VPL Bible/Commentary importer installmgr: command-line module installer mkfastmod: command-line module indexer mod2imp: export module to imp format mod2osis: export module to osis format mod2zmod: compress a sword module osis2mod: create Bible/Commentary/General Book from OSIS tei2mod: create Lexicon/Dictionary from TEI uconv: convert files from one character encoding to another vpl2mod: import from VPL file vs2osisreftxt: return an OSIS reference for any reference xml2gbs: import from OSIS/ThML to a General Book for more information, tutorials, and explanations of file formats, see http://cr osswire.org/wiki --------------------------------------- Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. You are running osis2mod: $Rev: 2571 $ OSIS Bible/commentary module creation tool for The SWORD Project usage: utils\osis2mod [OPTIONS] an existing folder that the module will be written path to the validated OSIS document, or '-' to read from standard input -a augment module if exists (default is to create new) -z use ZIP compression (default no compression) -Z use LZSS compression (default no compression) -b <2|3|4> compression block size (default 4): 2 - verse; 3 - chapter; 4 - book -c encipher module using supplied key (default no enciphering) -N do not convert UTF-8 or normalize UTF-8 to NFC (default is to convert to UTF-8, if needed, and then normalize to NFC) Note: UTF-8 texts should be normalized to NFC. -s <2|4> bytes used to store entry size (default is 2). Note: useful for commentaries with very large entries in uncompressed modules (2 bytes to store size equal 65535 characters) -v specify a versification scheme to use (default is KJV) Note: The following are valid values for v11n: Catholic Catholic2 German KJV KJVA Leningrad Luther MT NRSV NRSVA Synodal SynodalP Vulg -d turn on debugging (default is 0) Note: This flag may change in the future. Flags: The following are valid values: 0 - no debugging 1 - writes to module, very verbose 2 - verse start and end 4 - quotes, esp. Words of Christ 8 - titles 16 - inter-verse material 32 - BSP to BCV transformations 64 - v11n exceptions 128 - parsing of osisID and osisRef 256 - internal stack 512 - miscellaneous This argument can be used more than once. (Or the flags may be added together.) See http://www.crosswire.org/wiki/osis2mod for more details. here is some of the errors i am getting C:\Documents and Settings\Christopher Two>C:\Documents and Settings\Christopher Two>osis2mod <"C:\Documents and Settings\Christopher Two\My Documents\bible programming\Modules\text\ztext\bible"> <"C:\Documents and Settings\Christopher Two\My Documents\bible programming\osis\working File 3~.xml"> < was unexpected at this time. C:\Documents and Settings\Christopher Two\My Documents\bible programming\SWORD U TILITIES><"C:\Documents and Settings\Christop her Two\My Documents\bible programming\Modules\text\ztext\bible"> < was unexpected at this time. C:\Documents and Settings\Christopher Two\My Documents\bible programming\SWORD U TILITIES>"C:\Documents and Settings\Christopher Two\My Documents\bi ble programming\Modules\text\ztext\bible""C:\Documents and Settings\Chr istopher Two\My Documents\bible programming\osis\working File 3~.xml" The syntax of the command is incorrect. thank you for the help -------------- next part -------------- An HTML attachment was scrubbed... URL: From araj at critos.co.uk Sat Jan 26 07:39:12 2013 From: araj at critos.co.uk (araj at critos.co.uk) Date: Sat, 26 Jan 2013 14:39:12 -0000 Subject: [sword-devel] OSIS Message-ID: Can anyone tell me whether I can post OSIS-related questions here - and if not, whether there is somewhere else which handles them? Thanks, "Jamie" Jamieson -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sat Jan 26 07:55:47 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 06:55:47 -0800 (PST) Subject: [sword-devel] OSIS In-Reply-To: References: Message-ID: <1359212147515-4651825.post@n4.nabble.com> Hi Jamie, If after reading all the OSIS related pages in our developers' wiki, you still have OSIS related questions, then - yes - by all means ask them here. This list is very active (unlike some of our other lists). There'll be many messages that are probably "over your head" that relate to compiling SWORD etc. Yet the CrossWire community tries to be helpful (& patient) to respond to all questions posted here. Blessings! David -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-tp4651824p4651825.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sat Jan 26 08:13:57 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 07:13:57 -0800 (PST) Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: References: Message-ID: <1359213237723-4651826.post@n4.nabble.com> As a fellow Windows user (Win 7 x64) I found it useful to make (in my Sword directory) a symbolic link to where the Sword utilities are stored. Symbolic links may be unfamiliar to many Windows users, but old-hat to Linux folk. They are created using the Windows command called *mklink* You can use Windows Help to find out more. Then for any of the individual tasks (especially those that need repeating), I create a custom Windows CMD file to launch the utility, such that I can just double-click it to start that from within Windows Explorer. You can use any decent text editor (even Notepad will do) to make a CMD file. btw, I'd recommend *Notepad++* as a replacement for Notepad. Here's an example: I've been working on the Norsk module yesterday, so my CMD file called *MakeNorsk.cmd* contains: ..\utils2\imp2vs ..\Import\Norsk.raw.imp.edited.txt -z -o ..\modules\texts\ztext\norsk 1>..\log\imp2vs.log 2>..\log\error.log You see that I also capture the stdout and stderr streams to a pair of log files in a separate subfolder. It's also useful to append a pause command within the CMD file, so that you can watch what happens before the CMD window closes, and then close it manually. Also, to avoid clutter, all my CMD files are in a sub-directory I created under Sword (called Make). Likewise, source text files being used to make a module, these are in a folder I created (called Import). Once you've mastered these techniques, you'll wonder why you ever thought it difficult. Finally, for all utility commands relating to modules, the module name is Case Sensitive. It must be exactly as in the first line of the conf file, less the square brackets. This requirement appertains to all commands that do something with an existing module. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651826.html Sent from the SWORD Dev mailing list archive at Nabble.com. From araj at critos.co.uk Sat Jan 26 08:13:59 2013 From: araj at critos.co.uk (araj at critos.co.uk) Date: Sat, 26 Jan 2013 15:13:59 -0000 Subject: [sword-devel] OSIS questions Message-ID: I'm trying to convert a number of USFM documents to OSIS using my own software, and then to Sword using osis2mod. However, I'm relatively new to OSIS, and am struggling somewhat. Don't know if anyone can comment on any of the following issues? * : "Normalized name of the Bible version (Usually 3 letters for language, 3 for translation)". Does this have any significance to anything (ie does it matter that I get it "right")? If so, I assume the first three characters are the ISO language code? What should you do where you also have a variant code? Does the "translation" portion of the name need to follow any particular convention? * According to http://crosswire.org/wiki/OSIS_Bibles, the minimal document header consists of just . This does not seem at first sight to square with Appendix L of the OSIS user manual (dealing with conformance requirements), which appears to require a scope definition, to which the document must conform. Is the minimal header shown above in fact adequate? And what do you lose by not giving a fuller header (for example, by not giving "scope")? * An example text I have picked up includes the refSystem tag in a number of places. I'd prefer to avoid using this if I can, since it is not always immediately apparent what versification schemes have been used in the texts I have available to me. Is it a problem if the tag is not supplied? (If it must be supplied, then I presume it has to come from some predefined list of valid schemes? Where do you get the details of these schemes?) * http://crosswire.org/wiki/OSIS_Bibles includes
. I presume this enables you to group together, say OT or NT books? What are the implications of having it (or of not having it)? * OSIS appears to support a tableOfContents marker, which I believe corresponds to USFM toc/toc1/toc2/toc3. How is it used? Suppose I have the text for Matthew, and somewhere else I want a table of contents. Does the marker go at the start of Matthew itself, to mark the place to which the table of contents should point? Or does it go into the table of contents, to indicate that you want it to include a reference to Matthew? And either way what does the full tableOfContents tag look like? (I tried the former of the two options - putting
Matthew
into Matthew itself, but the only effect seemed to be that the word Matthew was output as part of the text.) * In at least one of the vernaculars I'm dealing with, the translator has included in the USFM at the start of each book both a "h" and an "mt" tag (in that order, in case it's of any interest). According to the OSIS user manual, both of these should give rise to title tags (of type "short" and "main" respectively, although I gather Sword ignores this). Unsurprisingly, I end up with two titles appearing at the start of the book. Clearly with a certain amount of effort I can address this by filtering the data while I'm generating the OSIS, but does OSIS itself (or Sword) have any convention as to what to do in these circumstances? * Some USFM tags appear to need to be converted into right-justified paragraphs. Does OSIS support right justification? * Occasionally we work with right-to-left languages in which the verse number needs to come at the end of the verse rather than the start, and in some cases also the verse number needs to be decorated in some manner. Does OSIS cater for this at all? Thanks in advance, "Jamie" Jamieson -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 8310 bytes Desc: not available URL: From dfhmch at googlemail.com Sat Jan 26 08:17:39 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 07:17:39 -0800 (PST) Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: <1359213237723-4651826.post@n4.nabble.com> References: <1359213237723-4651826.post@n4.nabble.com> Message-ID: <1359213459782-4651828.post@n4.nabble.com> PS. I forgot to mention that I generally make use of relative paths in referring to input and output files. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651828.html Sent from the SWORD Dev mailing list archive at Nabble.com. From scribe at crosswire.org Sat Jan 26 08:18:41 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sat, 26 Jan 2013 16:18:41 +0100 Subject: [sword-devel] Patches to fix compiler warnings In-Reply-To: <50D3A00E.8060909@ristioja.ee> References: <50D3A00E.8060909@ristioja.ee> Message-ID: <5103F3D1.7040808@crosswire.org> Jaak, Just getting to these sets of patches. sword-comparison-not-assignment-fix.diff.bz2 Applied. Thanks for finding this bug. On 12/21/2012 12:32 AM, Jaak Ristioja wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello! > > Please apply these patches (bzip2-ed to workaround sword-devel 90 KB > message size limit and attached) to fix about 3000 compiler warnings > with GCC and Clang. > > The patches should apply to https://crosswire.org/svn/sword/trunk at 2751 > > Blessings, > Jaak > > > PS: Here are the sha1sums: > > 7ba3a0b954b8b545d407eb0f46821e4ebdb1c3bf sword-Wempty-body-fix.diff.bz2 > e47776b086c1d8f686a09114bd162358db18a062 > sword-Wmissing-field-initializers-fix.diff.bz2 > fc68490a4aac0b8954fa02f0832fdccf95573fd7 sword-Wtype-limits-fix.diff.bz2 > eb2749fe94fcb8018be61c8925a12b2503460ac0 > sword-Wunused-parameter-fix.diff.bz2 > 004fbd6ac5bf6107cf37beb4b436f34400ec2774 > sword-comparison-not-assignment-fix.diff.bz2 > df8231f927ae1c34160b57d7b2a90e58a686448f > sword-illegal-source-file-encoding.diff.bz2 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iQgcBAEBAgAGBQJQ05/3AAoJEEqsYmEt1rCON2E//ArXCLZm2Mv0ERKpAoGTvDi+ > JHOOaTf7JW42DkloDiPqMbOSYyLBAbuyJQUp0cFg9pQWTe2TpGu5Fr5n46hsKYSc > FgFTM1fhVqimfeNt74425mxWKG9/DxuXskTI9MXLg6TwN/rVxr8kJpwqrYLnPy9C > 118zyvKCO0YBGAhGx1lkQXmpZbDAvzFszWD9lTHdknDJ/OhMZ12kjmAcpkzraPJ0 > H/KhWGxyGm2mlJ7HuBpKyhVz7oUO7kYBrj9CCBpQwnB17rOCglLqbRLodZIPnd30 > ufL8YjAlwpDvhcIW7CiwaBq23xUjOefReKoAJ6TOw4CQ6AqWvTADj0T/509QoUKg > ZfHBA0vQU0zxI4i67jmt86fI/2X3LuXNBdB9E+0wCLPxgVLuQImw3BufGdupkYe+ > Y3WddcRhtkWh/1yNhxBcB6hZoDZWTWs2iz4pIJYeO40pN6UZKC1MXLoAWqbufMfS > eN0sWDcC7cadq0hkgNLWkWe1fxPfdSwrWgOjICas44elCASBtnjOub9zWhh/HdOB > 668wCQtgBUo0ICdpdNAnsvIQiOhf60sgd99zvwczPeGgJKjvURzK/W4nS9UbwpUE > JESZfeQnLdOWJ2u+THozFLnjoOCw9c5NMZrFhGodVVb/u0bPQzyJ0Z1pT5/BZnOX > 1WC5PuQvGTBx/zepoLAuDLmh+SDqAhVm96fNTvhefY6oq78oQb+aG3N/mq64scXS > S+42S/BJWjDlz21AbfQJprkLOL3DbPBHOxG4/KdF8TFo73iNeTsPfLveumDbn6MS > DUwZETBZdOiGCLuBgmj9GIp/lMmQktdPJHv1JkdoLj+kL23oKR0MdvX5i+4rWOk/ > hs9D8JNCb+0bST71PUIW1HkF3elEYfZO/ciZ0U4mQVFFX/4VzXGJJqf5dh9HhCBZ > 3N1srhXGw4GEEblUv0oT2q+czeSDCjs/zLFQ7ONzbT9qoLOhEbI3cJ89A8hRbSC7 > 3u9OXKjyvJPWQvALxCu90QeS0ygqJPK/JZcHyc7I5J7m61SwhuPU7axKsRTGpHuT > X15w3SwaOz+P+r+WzRPj2OIcihBb4jnf+esk6ows7mNGa3jbm+UsGy/t2i5nb/p+ > DDoSnbxfTTpg9S9KOOrp6mTIZ9voCLXQAkEnx0E/1wu5xTgWI7aSSrXf5eO2JawP > riWTK9EaQ/yUf0SXhVsFKB948ATdoX45ag9OJfR1ShU27qaEE8BBgfGzXjYgcd/o > YujHVNhHfUD1xS8BF4D3G3LoO+l9m4d/iNtnXpc4JPd6f6ZuRGhKiM8V3N7olYYC > 3Xf4hX9V4S2txrPX0XXG5Zq4x90Jx8VxbjN1UKMjTKRgfhghh4c0EzVvpq47sF7z > qtULiOLlbEPUlH78nTu8eZ4Vy1DFhG2BEOSzWZatvO4UxiioewnQtp987ZG7Cpzy > I2RRqrL4vv4FQ2UvOCEqVwYuZTSckcG18Bfy9FjqzH6WW/idBBUzWDrOgcEnke34 > 0A+hQtNo8+WMKD9zBdGEGY8ymNk/lj7F2JAvEhvvdXYemsDBiVfrezCj7EA7ybZp > c8Oisk+EZgo4FMV49ytnjWR1rlsS7wCtLJb1GLjWOggIesrNq8rg9P7j8/u3U/GZ > HDj/UsxInZcZv91u60r8oEl90vdP3hXJxdowKXjRBODFBmfQkJTFYoPd1JIOqyvT > 1eGoYZ/o6ClGbEwcg8XEMOo2MvoF889b/yOOjP6kPt/tQUviwug2McU/KmNThqvU > Arw/+8c/XpW/69SOHIBzgSS1ipcjOafn4k5g8bgkRknx97FaBBQNG9AqYl0iHlMS > LwT9n6gPPBp3lF9LSWlzPvh0+vMQKfH4cwuIQMGwzhd156OkfYmfskoBCDv3VDhh > mhhH502LOleMfoHajzo2IXc2IFToVxZq8rwhWwipXmEoOIH9DpbaaRwgbSjXQr72 > xerD7lzChmTqriH3TmhLXIe5IGpLhPJZOw4AMyuTC3IVvSvMyE4SX/9UHOvxHB3v > sI9OfimIn2NCfsbxLI+0SI8cw7BlSHE63OJjp7yG7oVqbLL7T8VqK5uTgAHWuy16 > HebEXEs5yJtiSh1s2BQX5qxIOs9IFORBtgVlaTFozaVDMk+HMhHSN+pxb49vel0P > ME7AOf1zIxqs1zFeZuqCRRzT8z3UoWcbu5maluSDyyI08i+1nzKDvRMW+77UrAWD > 6sQD+JrHDQoUK8fu3OtUbUaOSyLW5bJ5+MeHEnsPrgvxC+B2lZYw9Bz5QCUSs6xu > FhC7N1OlfM8b+e0EE0IAD2nwTvl0IcJFgbFMEm6KIy2dA6ChoPkTSbi3l0Nm2y7r > iX57mdzKrgcRfUXkFWTrfDx8951qQpw16HNjwCa0zgNbrvKbEFqPzvEPzkNlWw0S > E992keRPJNzpEXe9ZWZUE+qr92CsyqwAvPZ1z1jUT7swIKqrl7/O33CxiK2Iifoc > BRV15T5V8LzWiO0MgOb85UsXZjwSxHMw8theHRAKvqKF0ti8ospgCirEU9ZTv7VF > pSqFVOUBCgWkCtcGE8GaLg7eEleTx5inliILgD6kC+80CV8j1f3L6P2+zLMDxQeo > W/cqdkbk8oL6yoOdRGMXuozPu3g7MQZUDYQplLxGcxYk3fDb2DKgiJw57Rlo+5ji > O7I7wqWI88nEuku0wUIe11ydDSGtYGoOvRC0C4T/Z6vsvd/oNcQAb4tjrjqtKIlY > OdqdFXYt+xF3RepeinW5 > =jSQt > -----END PGP SIGNATURE----- > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sat Jan 26 08:33:33 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 07:33:33 -0800 (PST) Subject: [sword-devel] SWORD utilities for Windows In-Reply-To: References: Message-ID: <1359214413287-4651830.post@n4.nabble.com> This reply is merely to alert new members to the location of Greg's most recent build of the Sword utilities. Christopher Brown may find this especially useful. After the current round of patches to SWORD ends up with a proper release of the engine, if the utils need to be recompiled, I trust Greg will again take the initiative. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/SWORD-utilities-for-Windows-tp4651209p4651830.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sat Jan 26 08:35:41 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 07:35:41 -0800 (PST) Subject: [sword-devel] SWORD utilities for Windows In-Reply-To: <1359214413287-4651830.post@n4.nabble.com> References: <1359214413287-4651830.post@n4.nabble.com> Message-ID: <1359214541910-4651831.post@n4.nabble.com> Ooops! Just in case you don't have the past threads in your email client, this was Greg's message. If you want the latest build of the SWORD utilities for Windows - version 2741 - they're available from http://dl.thehellings.com/mingw32/r2741.zip These include the Xiphos patch to properly handle path names that contain non-ASCII characters. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/SWORD-utilities-for-Windows-tp4651209p4651831.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dmsmith at crosswire.org Sat Jan 26 09:05:21 2013 From: dmsmith at crosswire.org (DM Smith) Date: Sat, 26 Jan 2013 11:05:21 -0500 Subject: [sword-devel] OSIS questions In-Reply-To: References: Message-ID: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> Others should chime in too. This just a partial answer. Basic overview: OSIS should be written to the OSIS specification. We recommend a document centric representation where Book, Chapter, Section, Paragraph, Line Group and Lines are dominant and verse elements are milestoned. This is transformed by osis2mod into Book, Chapter, Verse representation. Front-ends then use a SWORD renderer to transform module content into presentational output. This is driven by values in a module's conf. So questions regarding OSIS fall into: How should it be done in OSIS. How does osis2mod handle it. And how do SWORD renderers handle such and so content. On Jan 26, 2013, at 10:13 AM, wrote: > I'm trying to convert a number of USFM documents to OSIS using my own > software, and then to Sword using osis2mod. However, I'm relatively new to > OSIS, and am struggling somewhat. Don't know if anyone can comment on any > of the following issues? Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. > > * : "Normalized name of the Bible > version (Usually 3 letters for language, 3 for translation)". Does this > have any significance to anything (ie does it matter that I get it "right")? > If so, I assume the first three characters are the ISO language code? What > should you do where you also have a variant code? Does the "translation" > portion of the name need to follow any particular convention? The documentation that we've provided relates to an OSIS document used as a source for a SWORD module. Most of our answers will also be SWORD centric. To SWORD, the value does not matter. Osis2mod strips out everything until the first meaningful
element. At some time in the future, osis2mod will examine the header info to provide a best guess for key conf elements. > > * According to http://crosswire.org/wiki/OSIS_Bibles, the minimal > document header consists of just . This does not > seem at first sight to square with Appendix L of the OSIS user manual > (dealing with conformance requirements), which appears to require a scope > definition, to which the document must conform. Is the minimal header shown > above in fact adequate? And what do you lose by not giving a fuller header > (for example, by not giving "scope")? In a SWORD context, you lose nothing. At least until we improve osis2mod to suggest a conf. But it is a great place to document information that will be helpful to you or others later. > > * An example text I have picked up includes the refSystem tag in a > number of places. I'd prefer to avoid using this if I can, since it is not > always immediately apparent what versification schemes have been used in the > texts I have available to me. Is it a problem if the tag is not supplied? > (If it must be supplied, then I presume it has to come from some predefined > list of valid schemes? Where do you get the details of these schemes?) > Reference systems are rather bothersome. Your goal is to determine the best fit of those that SWORD provides. IIRC, Greg has put together a script that'll help figure out which reference system (which osis2mod refers to as a "versification" system) is most encompassing. Osis2mod is good in that it retains all verse material. But when you pick the wrong ref system, osis2mod will warn you that the verse is not in the versification and that it is being appended to the prior verse. The details are rather cryptic (held in arrays in SWORD header files.) Basically most of us just try each one to see which has the least warnings. And from there try to understand those warnings. Chris has defined these. So he might be able to clarify. > * http://crosswire.org/wiki/OSIS_Bibles includes
type="bookGroup">. I presume this enables you to group together, say OT or > NT books? What are the implications of having it (or of not having it)? It is not needed for a SWORD module. All that osis2mod requires are the
Having it has no impact. > > * OSIS appears to support a tableOfContents marker, which I believe > corresponds to USFM toc/toc1/toc2/toc3. How is it used? Suppose I have the > text for Matthew, and somewhere else I want a table of contents. Does the > marker go at the start of Matthew itself, to mark the place to which the > table of contents should point? Or does it go into the table of contents, > to indicate that you want it to include a reference to Matthew? And either > way what does the full tableOfContents tag look like? (I tried the former > of the two options - putting
Matthew
into > Matthew itself, but the only effect seemed to be that the word Matthew was > output as part of the text.) I don't know the answer to this specifically (how to encode it properly in OSIS), but can give insight into how it might be handled by SWORD. The SWORD rendering of a module does not handle Table of Contents, but to output it as inline, unstructured text. (I think I have this right.) Basically, notes and references are out of line content to SWORD. All else is in line. IIRC, if a SWORD render sees a tag it doesn't understand, it merely processes the contents as if the tag was not there. What some of us do is have a fully specified OSIS file and then prune (using xslt) that which SWORD doesn't handle well, to produce input to osis2mod. > > * In at least one of the vernaculars I'm dealing with, the translator > has included in the USFM at the start of each book both a "h" and an "mt" > tag (in that order, in case it's of any interest). According to the OSIS > user manual, both of these should give rise to title tags (of type "short" > and "main" respectively, although I gather Sword ignores this). > Unsurprisingly, I end up with two titles appearing at the start of the book. > Clearly with a certain amount of effort I can address this by filtering the > data while I'm generating the OSIS, but does OSIS itself (or Sword) have any > convention as to what to do in these circumstances? > Osis2mod uses the type="main" on a title to indicate that a title between the start of a chapter and the first verse is a chapter title (and stuffed in a verse 0 slot) and not a verse title (stuffed in a verse 1 slot). SWORD renders don't care. > * Some USFM tags appear to need to be converted into right-justified > paragraphs. Does OSIS support right justification? I don't know if OSIS supports it (would need to look), but SWORD renderers do not. Same with JSword renderers. > > * Occasionally we work with right-to-left languages in which the verse > number needs to come at the end of the verse rather than the start, and in > some cases also the verse number needs to be decorated in some manner. Does > OSIS cater for this at all? Actually, it merely has the visual appearance to LtoR language readers that it is at the end of the verse. Actually, it is at the start, but appears at the right. This is handled by front-ends. In the SWORD module's conf, it needs the Direction= attribute set to pick up the orientation. JSword doesn't use the value but uses the Language code. In His Service, DM > > > Thanks in advance, > > "Jamie" Jamieson > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dfhmch at googlemail.com Sat Jan 26 10:13:30 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 09:13:30 -0800 (PST) Subject: [sword-devel] OSIS questions In-Reply-To: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> References: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> Message-ID: <1359220410665-4651833.post@n4.nabble.com> DM wrote, Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. ----- To which it may be useful to add that Chris has developed (but not yet released) a more comprehensive Python script to convert USFM to OSIS. Download from http://www.crosswire.org/svn/sword-tools/trunk/modules/python/ Any useful test results or issues with his new script should be reported via our tracker. http://www.crosswire.org/tracker/browse/MODTOOLS David PS. The developer of xulsword has also developed his own script to convert USFM to OSIS. -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-questions-tp4651827p4651833.html Sent from the SWORD Dev mailing list archive at Nabble.com. From chris at burrell.me.uk Sat Jan 26 10:36:58 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 26 Jan 2013 17:36:58 +0000 Subject: [sword-devel] OSIS questions In-Reply-To: <1359220410665-4651833.post@n4.nabble.com> References: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> <1359220410665-4651833.post@n4.nabble.com> Message-ID: Yes, Kahunapule Michael Johnson has built Haiola. Recently he's made a big effort to get USFM/USFX texts into OSIS format. You can find Haiola here: http://haiola.org/ Chris On 26 January 2013 17:13, David Haslam wrote: > DM wrote, > > Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You > might find that helpful. Off hand I don't know where that is. You can get > more information by searching this list or from them. > > Also, Kahunapule Michael Johnson on this list has converters that he uses. > He has many, many texts in USFM. > > ----- > > To which it may be useful to add that Chris has developed (but not yet > released) a more comprehensive Python script to convert USFM to OSIS. > > Download from > http://www.crosswire.org/svn/sword-tools/trunk/modules/python/ > > Any useful test results or issues with his new script should be reported > via > our tracker. > > http://www.crosswire.org/tracker/browse/MODTOOLS > > David > > PS. The developer of xulsword has > also developed his own script to convert USFM to OSIS. > > > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/OSIS-questions-tp4651827p4651833.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at burrell.me.uk Sat Jan 26 12:09:37 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 26 Jan 2013 19:09:37 +0000 Subject: [sword-devel] Swahili localisation Message-ID: Hi I'd like to find out if anybody has some Swahili Bible Names/abbreviations. I can't find these in either JSword or Sword libraries. Perhaps this has never been done. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sat Jan 26 12:26:03 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 11:26:03 -0800 (PST) Subject: [sword-devel] Swahili localisation In-Reply-To: References: Message-ID: <1359228363891-4651836.post@n4.nabble.com> I have the book names for the kiSwahili NT: Book: Matayo Book: Marko Book: Luka Book: Yohana Book: Matendo Ya Mitume Book: Warumi Book: 1 Wakorintho Book: 2 Wakorintho Book: Wagalatia Book: Waefeso Book: Wafilipi Book: Wakolosai Book: 1 Wathesalonike Book: 2 Wathesalonike Book: 1 Timotheo Book: 2 Timotheo Book: Tito Book: Filemoni Book: Waebrania Book: Yakobo Book: 1 Petro Book: 2 Petro Book: 1 Yohana Book: 2 Yohana Book: 3 Yohana Book: Yuda Book: Ufunua was Yohana ---- Notes: Revelation (without the "of John") is Ufunuo. Psalms is Zaburi If you require OT book names, I can put you in contact with someone in WBT who visits Tanzania. If you require the verbose book names for the NT, I could readily transcribe them from my printed edition of the 2001 Union Version. NB. Many online editions of the Swahili NT still omit Philippians. David Haslam -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651836.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sat Jan 26 12:28:31 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 11:28:31 -0800 (PST) Subject: [sword-devel] Swahili localisation In-Reply-To: References: Message-ID: <1359228511313-4651837.post@n4.nabble.com> The full 66 book names are displayed as hyperlinks here: http://www.biblica.com/bibles/swahili/ David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651837.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sat Jan 26 12:33:34 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 11:33:34 -0800 (PST) Subject: [sword-devel] Swahili localisation In-Reply-To: References: Message-ID: <1359228814702-4651838.post@n4.nabble.com> See also https://sw.wikipedia.org/wiki/Agano_Jipya https://sw.wikipedia.org/wiki/Agano_la_Kale David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651838.html Sent from the SWORD Dev mailing list archive at Nabble.com. From chris at burrell.me.uk Sat Jan 26 12:36:22 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sat, 26 Jan 2013 19:36:22 +0000 Subject: [sword-devel] Swahili localisation In-Reply-To: <1359228814702-4651838.post@n4.nabble.com> References: <1359228814702-4651838.post@n4.nabble.com> Message-ID: Hi David Thanks for these. I'd done a few searches on Google and wikipedia myself. The issue is with finding the abbreviations. So thanks for the links above. It gives us the Swahili NT abbreviations. Chris On 26 January 2013 19:33, David Haslam wrote: > See also > > https://sw.wikipedia.org/wiki/Agano_Jipya > > https://sw.wikipedia.org/wiki/Agano_la_Kale > > David > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651838.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kahunapule at mpj.cx Sat Jan 26 12:55:06 2013 From: kahunapule at mpj.cx (Kahunapule Michael Johnson) Date: Sat, 26 Jan 2013 09:55:06 -1000 Subject: [sword-devel] OSIS questions In-Reply-To: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> References: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> Message-ID: <5104349A.9000500@mpj.cx> An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sat Jan 26 13:01:03 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sat, 26 Jan 2013 12:01:03 -0800 (PST) Subject: [sword-devel] Swahili localisation In-Reply-To: References: <1359228814702-4651838.post@n4.nabble.com> Message-ID: <1359230463349-4651841.post@n4.nabble.com> The key to success was some lateral thinking, and remembering that Wikipedia has projects in 285 languages. With a bit of ingenuity, one can probably use the same method to find the book names and abbreviations for a high proportion of these languages. The point I made about the book of Philippians being missing also applies to our Swahili SWORD module! http://www.crosswire.org/tracker/browse/MOD-86 David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651841.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sun Jan 27 01:37:58 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 27 Jan 2013 00:37:58 -0800 (PST) Subject: [sword-devel] Swahili localisation In-Reply-To: <1359228363891-4651836.post@n4.nabble.com> References: <1359228363891-4651836.post@n4.nabble.com> Message-ID: <1359275878512-4651842.post@n4.nabble.com> OT Swahili abbreviations are in parentheses. GEN - Genesis (Mwa) EXO - Exodus (Kut) LEV - Leviticus (Law) NUM - Numbers (Hes) DEU - Deuteronomy (Kum) JOS - Joshua (Yos) JDG - Judges (Amu) RUT - Ruth (Rut) 1SA - 1 Samuel (1 Sam) 2SA - 2 Samuel (2 Sam) 1KI - 1 Kings (1 Fal) 2KI - 2 Kings (2 Fal) 1CH - 1 Chronicles (1 Nya) 2CH - 2 Chronicles (2 Nya) EZR - Ezra (Ezr) NEH - Nehemiah (Neh) EST - Esther (Hebrew) (Est) JOB - Job (Ayu) PSA - Psalms (Zab) PRO - Proverbs (Mit) ECC - Ecclesiastes (Mhu) SNG - Song of Songs (Wim) ISA - Isaiah (Isa) JER - Jeremiah (Yer) LAM - Lamentations (Omb) EZK - Ezekiel (Eze) DAN - Daniel (Hebrew) (Dan) HOS - Hosea (Hos) JOL - Joel (Yoe) AMO - Amos (Amo) OBA - Obadiah (Oba) JON - Jonah (Yon) MIC - Micah (Mik) NAM - Nahum (Nah) HAB - Habakkuk (Hab) ZEP - Zephaniah (Sef) HAG - Haggai (Hag) ZEC - Zechariah (Zek) MAL - Malachi (Mal) David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651842.html Sent from the SWORD Dev mailing list archive at Nabble.com. From araj at critos.co.uk Sun Jan 27 02:13:53 2013 From: araj at critos.co.uk (ARA Jamieson) Date: Sun, 27 Jan 2013 09:13:53 -0000 Subject: [sword-devel] OSIS questions In-Reply-To: <5104349A.9000500@mpj.cx> References: <25C33135-43FF-4F29-AC2A-A300EC8CD911@crosswire.org> <5104349A.9000500@mpj.cx> Message-ID: <499C4FA28E104922AAB31189A4ED8E73@Makyra1> Thank you very much - will do. Jamie _____ From: Kahunapule Michael Johnson [mailto:kahunapule at mpj.cx] Sent: 26 January 2013 19:55 To: sword-devel at crosswire.org Subject: Re: [sword-devel] OSIS questions On 01/26/2013 06:05 AM, DM Smith wrote: On Jan 26, 2013, at 10:13 AM, wrote: > I'm trying to convert a number of USFM documents to OSIS using my own > software, and then to Sword using osis2mod. However, I'm relatively new to > OSIS, and am struggling somewhat. Don't know if anyone can comment on any > of the following issues? Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. Please see http://haiola.org if you are interested in open source C# software that converts USFM to OSIS. It might give you a head start... -- Aloha, Michael Johnson mljohnson.org PO BOX 5278 KAILUA KONA HI 96745-5278 USA Phone: +1 808-333-6921 Skype: kahunapule -------------- next part -------------- An HTML attachment was scrubbed... URL: From 5001 at hotmail.com Sun Jan 27 04:37:10 2013 From: 5001 at hotmail.com (Pola Edward) Date: Sun, 27 Jan 2013 13:37:10 +0200 Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: References: Message-ID: To use utilities Go to the Utilities Folder , Shift + Right Click >> Open Command Window Here You may need this power toy from microsoft for "Open Command Window Here" on XP, it exists by default in Windows 7 http://go.microsoft.com/fwlink/?LinkId=211471 Now you have Command Prompt opened in the utilities directory this is an example for Mod2Osis utility (Note It's Case Sensitive) This Command will convert the Installed KJV Module to Osis Xml file mod2osis kjv>kjv.xml ------------------------------------- Another utility to convert Osis to Module is osis2mod Command osis2mod Matt1 Matt.xml Matt1 is the output destination folder Matt.xml is the Osis Source text Again, it's case sensitive so Matt is NOT Equal matt Also it's better to install any sword frontend like Xiphos Best Regards, Pola From: christopherbr7 at hotmail.com To: sword-devel at crosswire.org Date: Fri, 25 Jan 2013 18:09:40 -0500 Subject: [sword-devel] Hello, I need help with the Sword Utilities I have been trying to run the sword utilities for about a week now. i have tried to find information on the exact line to use in the command prompt i am running windows xp sp3, osis2mod wont run from the folder it is in, i have to run it from cmd. When i run it from the folder it appears breifly and dissappears, so i have to drag the exe to the command prompt, i dont know if this is normal. if someone could paste an example of what string to use to make a module that would be great. Here is some of what i have tried through the prompt C:\Documents and Settings\All Users\Application Data\Sword>echo off ------------------------------------------ addld: Lexicon and Dictionary creation tool diatheke: multi-purpose command-line frontend imp2gbs: General Book creation tool imp2ld: Lexicon and Dictionary creation tool imp2vs: VPL Bible/Commentary importer installmgr: command-line module installer mkfastmod: command-line module indexer mod2imp: export module to imp format mod2osis: export module to osis format mod2zmod: compress a sword module osis2mod: create Bible/Commentary/General Book from OSIS tei2mod: create Lexicon/Dictionary from TEI uconv: convert files from one character encoding to another vpl2mod: import from VPL file vs2osisreftxt: return an OSIS reference for any reference xml2gbs: import from OSIS/ThML to a General Book for more information, tutorials, and explanations of file formats, see http://cr osswire.org/wiki --------------------------------------- Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. You are running osis2mod: $Rev: 2571 $ OSIS Bible/commentary module creation tool for The SWORD Project usage: utils\osis2mod [OPTIONS] an existing folder that the module will be written path to the validated OSIS document, or '-' to read from standard input -a augment module if exists (default is to create new) -z use ZIP compression (default no compression) -Z use LZSS compression (default no compression) -b <2|3|4> compression block size (default 4): 2 - verse; 3 - chapter; 4 - book -c encipher module using supplied key (default no enciphering) -N do not convert UTF-8 or normalize UTF-8 to NFC (default is to convert to UTF-8, if needed, and then normalize to NFC) Note: UTF-8 texts should be normalized to NFC. -s <2|4> bytes used to store entry size (default is 2). Note: useful for commentaries with very large entries in uncompressed modules (2 bytes to store size equal 65535 characters) -v specify a versification scheme to use (default is KJV) Note: The following are valid values for v11n: Catholic Catholic2 German KJV KJVA Leningrad Luther MT NRSV NRSVA Synodal SynodalP Vulg -d turn on debugging (default is 0) Note: This flag may change in the future. Flags: The following are valid values: 0 - no debugging 1 - writes to module, very verbose 2 - verse start and end 4 - quotes, esp. Words of Christ 8 - titles 16 - inter-verse material 32 - BSP to BCV transformations 64 - v11n exceptions 128 - parsing of osisID and osisRef 256 - internal stack 512 - miscellaneous This argument can be used more than once. (Or the flags may be added together.) See http://www.crosswire.org/wiki/osis2mod for more details. here is some of the errors i am getting C:\Documents and Settings\Christopher Two>C:\Documents and Settings\Christopher Two>osis2mod <"C:\Documents and Settings\Christopher Two\My Documents\bible programming\Modules\text\ztext\bible"> <"C:\Documents and Settings\Christopher Two\My Documents\bible programming\osis\working File 3~.xml"> < was unexpected at this time. C:\Documents and Settings\Christopher Two\My Documents\bible programming\SWORD U TILITIES><"C:\Documents and Settings\Christop her Two\My Documents\bible programming\Modules\text\ztext\bible"> < was unexpected at this time. C:\Documents and Settings\Christopher Two\My Documents\bible programming\SWORD U TILITIES>"C:\Documents and Settings\Christopher Two\My Documents\bi ble programming\Modules\text\ztext\bible""C:\Documents and Settings\Chr istopher Two\My Documents\bible programming\osis\working File 3~.xml" The syntax of the command is incorrect. thank you for the help _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sun Jan 27 06:26:36 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 27 Jan 2013 05:26:36 -0800 (PST) Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: References: Message-ID: <1359293196352-4651845.post@n4.nabble.com> Just a general reminder. mod2osis is a deprecated Sword utility. You can search the sword-devel archives to find out why. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651845.html Sent from the SWORD Dev mailing list archive at Nabble.com. From scribe at crosswire.org Sun Jan 27 07:13:18 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sun, 27 Jan 2013 15:13:18 +0100 Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: <1359293196352-4651845.post@n4.nabble.com> References: <1359293196352-4651845.post@n4.nabble.com> Message-ID: <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> Well, mod2osis is a reference objective for the filters. Some day the osis2mod + osisosis filter set will perform a well enough to allow a simple module iteration and output to support a lossless round trip using osis2mod and mod2osis. Greg has submitted patches to mod2osis to bring this really close, but to reiterate, the goal for mod2osis is not to produce an export utility, but to be a reference objective to improve the engine's import and filters. So, 'deprecate' is not exactly how I would label mod2osis, but practically for end users, it's the same, Troy David Haslam wrote: >Just a general reminder. > >mod2osis is a deprecated Sword utility. > >You can search the sword-devel archives to find out why. > >David > > > >-- >View this message in context: >http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651845.html >Sent from the SWORD Dev mailing list archive at Nabble.com. > >_______________________________________________ >sword-devel mailing list: sword-devel at crosswire.org >http://www.crosswire.org/mailman/listinfo/sword-devel >Instructions to unsubscribe/change your settings at above page -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Sun Jan 27 07:49:41 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 27 Jan 2013 06:49:41 -0800 (PST) Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> References: <1359293196352-4651845.post@n4.nabble.com> <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> Message-ID: <1359298181865-4651847.post@n4.nabble.com> Thanks Troy, for the clarification. Anyone wishing to assist in the programming task started by Greg can find his branch here: https://code.launchpad.net/~greg-hellings/sword/mod2osis See also http://crosswire.org/wiki/Mod2osis#Current_status David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651847.html Sent from the SWORD Dev mailing list archive at Nabble.com. From arthurbolstad at sbcglobal.net Sun Jan 27 07:30:35 2013 From: arthurbolstad at sbcglobal.net (Arthur Bolstad) Date: Sun, 27 Jan 2013 08:30:35 -0600 Subject: [sword-devel] Swahili localisation In-Reply-To: <1359275878512-4651842.post@n4.nabble.com> References: <1359228363891-4651836.post@n4.nabble.com> <1359275878512-4651842.post@n4.nabble.com> Message-ID: <51053A0B.4060405@sbcglobal.net> An excellent resource center for Kisswahili would be Lutherans In Africa as they do regular translation into Kisswahili. They have experienced translators approved by the Lutheran Churchs in Kenya and Tanzania. http://www.lutheransinafrica.com Arthur Bolstad On 1/27/2013 2:37 AM, David Haslam wrote: > OT Swahili abbreviations are in parentheses. > > GEN - Genesis (Mwa) > EXO - Exodus (Kut) > LEV - Leviticus (Law) > NUM - Numbers (Hes) > DEU - Deuteronomy (Kum) > JOS - Joshua (Yos) > JDG - Judges (Amu) > RUT - Ruth (Rut) > 1SA - 1 Samuel (1 Sam) > 2SA - 2 Samuel (2 Sam) > 1KI - 1 Kings (1 Fal) > 2KI - 2 Kings (2 Fal) > 1CH - 1 Chronicles (1 Nya) > 2CH - 2 Chronicles (2 Nya) > EZR - Ezra (Ezr) > NEH - Nehemiah (Neh) > EST - Esther (Hebrew) (Est) > JOB - Job (Ayu) > PSA - Psalms (Zab) > PRO - Proverbs (Mit) > ECC - Ecclesiastes (Mhu) > SNG - Song of Songs (Wim) > ISA - Isaiah (Isa) > JER - Jeremiah (Yer) > LAM - Lamentations (Omb) > EZK - Ezekiel (Eze) > DAN - Daniel (Hebrew) (Dan) > HOS - Hosea (Hos) > JOL - Joel (Yoe) > AMO - Amos (Amo) > OBA - Obadiah (Oba) > JON - Jonah (Yon) > MIC - Micah (Mik) > NAM - Nahum (Nah) > HAB - Habakkuk (Hab) > ZEP - Zephaniah (Sef) > HAG - Haggai (Hag) > ZEC - Zechariah (Zek) > MAL - Malachi (Mal) > > David > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651842.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > From chris at burrell.me.uk Sun Jan 27 09:03:27 2013 From: chris at burrell.me.uk (Chris Burrell) Date: Sun, 27 Jan 2013 16:03:27 +0000 Subject: [sword-devel] Swahili Bible names Message-ID: Hi FYI, I've committed to JSword the set of Swahili Bible Names (without the extra books). Thanks to David Haslam + 2 of my Swahili contacts, there are a couple of variations. The file can be found here: https://github.com/tyndale/jsword/blob/32e5e80ed04db42975c099cb46baa877b043da70/src/main/resources/BibleNames_sw.properties It shouldn't be difficult for someone to transform this into a Sword Locale file. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Sun Jan 27 13:44:27 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Sun, 27 Jan 2013 21:44:27 +0100 Subject: [sword-devel] BibleCS 1.7.0RC1 Message-ID: <510591AB.6030306@crosswire.org> OK Guys, We've had this update sitting out there for years now and I've finally fixed the last reported bugs from the last RC I sent out (a long long time ago). Without considering the usefulness of BibleCS against our other actively developed Windows frontends, this update at least includes an InstallManager which can migrate books out to the public location we've all agreed our books should be installed to, so other frontends can share the same library of materials. And it is also compiled against latest SVN head, so all module versifications should work with it. One other thing I did was update the installer tree controls to work with wide characters, so you should see multibyte UTF8 strings display ok now in the InstallManager. Have a go and let me know if you see anything which needs updating before posting this publicly: http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC1.exe Troy From dfhmch at googlemail.com Sun Jan 27 14:17:31 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 27 Jan 2013 13:17:31 -0800 (PST) Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <510591AB.6030306@crosswire.org> References: <510591AB.6030306@crosswire.org> Message-ID: <1359321451236-4651851.post@n4.nabble.com> I stopped using BibleCS when I bought my Windows 7 (x64) PC (Toshiba Satellite C650). It was installed in my (defunct) Windows XP machine, which I had to replace in August 2010. I've downloaded Troy's new RC, but not yet decided whether to install it. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651851.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Sun Jan 27 14:29:38 2013 From: dfhmch at googlemail.com (David Haslam) Date: Sun, 27 Jan 2013 13:29:38 -0800 (PST) Subject: [sword-devel] Vertical whitespace In-Reply-To: <1358756920815-4651722.post@n4.nabble.com> References: <88779976-CE1C-4F94-B6B2-B685C3C25752@crosswire.org> <1358756920815-4651722.post@n4.nabble.com> Message-ID: <1359322178089-4651852.post@n4.nabble.com> Example: Excessive vertical white space is especially 'annoying' in the *HinERV* module when viewed in *Xiphos* with Headings displayed. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Vertical-whitespace-tp4651708p4651852.html Sent from the SWORD Dev mailing list archive at Nabble.com. From DavidTroidl at aol.com Sun Jan 27 15:00:28 2013 From: DavidTroidl at aol.com (David Troidl) Date: Sun, 27 Jan 2013 17:00:28 -0500 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <510591AB.6030306@crosswire.org> References: <510591AB.6030306@crosswire.org> Message-ID: <5105A37C.2080501@aol.com> Hi Troy, I just installed it on Windows 7. The install went fine. Just a cursory testing reveals nothing, except when I turned on morphology and decided to change the color from neon green to something more readable, it internally turned off the morphology. It took a minute to figure out. I don't know if that's the desired behavior. If there's anything specific you want checked, let me know. Peace, David On 1/27/2013 3:44 PM, Troy A. Griffitts wrote: > OK Guys, > > We've had this update sitting out there for years now and I've finally > fixed the last reported bugs from the last RC I sent out (a long long > time ago). Without considering the usefulness of BibleCS against our > other actively developed Windows frontends, this update at least > includes an InstallManager which can migrate books out to the public > location we've all agreed our books should be installed to, so other > frontends can share the same library of materials. And it is also > compiled against latest SVN head, so all module versifications should > work with it. One other thing I did was update the installer tree > controls to work with wide characters, so you should see multibyte > UTF8 strings display ok now in the InstallManager. > > Have a go and let me know if you see anything which needs updating > before posting this publicly: > > http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC1.exe > > Troy > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From thulester at gmail.com Sun Jan 27 15:34:10 2013 From: thulester at gmail.com (Andrew Thule) Date: Sun, 27 Jan 2013 17:34:10 -0500 Subject: [sword-devel] Python Build Errors (Ubuntu) Message-ID: I continue to get the following build errors with the python bindings using the following: #cmake -DSWORD_BINDINGS="Perl Python" ../sword .... CUT ... [ 90%] Generating Sword.cxx /usr/local/src/sword/include/multimapwdef.h:26: Warning 389: operator[] ignored (consider using %extend) /usr/local/src/sword/include/versemgr.h:124: Warning 325: Nested class not currently supported (Book ignored) /usr/local/src/sword/include/versemgr.h:149: Warning 325: Nested class not currently supported (System ignored) /usr/local/src/sword/include/treekey.h:61: Warning 325: Nested class not currently supported (PositionChangeListener ignored) running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying Sword.py -> build/lib.linux-x86_64-2.7 running build_ext building '_Sword' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/local/src/sword/bindings/swig/python -I/usr/local/src/sword/include -I/usr/local/src/sword/bindings/swig/python/.. -I/usr/local/src/sword/bindings/swig/python../../ -I/usr/include/python2.7 -c Sword.cxx -o build/temp.linux-x86_64-2.7/Sword.o cc1plus: warning: command line option ?-Wstrict-prototypes? is valid for Ada/C/ObjC but not for C++ [enabled by default] Sword.cxx: In function ?PyObject* _wrap_SWDisplay_Display(PyObject*, PyObject*)?: Sword.cxx:44967:43: warning: ?char sword::SWDisplay::Display(sword::SWModule&)? is deprecated (declared at /usr/local/src/sword/include/swdisp.h:50) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_StripText__SWIG_0(PyObject*, PyObject*)?: Sword.cxx:49480:65: warning: ?const char* sword::SWModule::StripText(const char*, int)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_StripText__SWIG_1(PyObject*, PyObject*)?: Sword.cxx:49521:60: warning: ?const char* sword::SWModule::StripText(const char*, int)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_StripText__SWIG_2(PyObject*, PyObject*)?: Sword.cxx:49552:42: warning: ?const char* sword::SWModule::StripText(const char*, int)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:634) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_RenderText__SWIG_0(PyObject*, PyObject*)?: Sword.cxx:49850:71: warning: ?const char* sword::SWModule::RenderText(const char*, int, bool)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_RenderText__SWIG_1(PyObject*, PyObject*)?: Sword.cxx:49900:66: warning: ?const char* sword::SWModule::RenderText(const char*, int, bool)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_RenderText__SWIG_2(PyObject*, PyObject*)?: Sword.cxx:49941:61: warning: ?const char* sword::SWModule::RenderText(const char*, int, bool)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations] Sword.cxx: In function ?PyObject* _wrap_SWModule_RenderText__SWIG_3(PyObject*, PyObject*)?: Sword.cxx:49972:43: warning: ?const char* sword::SWModule::RenderText(const char*, int, bool)? is deprecated (declared at /usr/local/src/sword/include/swmodule.h:645) [-Wdeprecated-declarations] g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-x86_64-2.7/Sword.o -L/usr/local/src/cmakebuild -lsword -o build/lib.linux-x86_64-2.7/_Sword.so (From here on it seems successful and sword works save for the python bindings) When I try to use the python binding, it fails. I believe that these build errors are the problem. Any ideas about why this is failing? ~A -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhphx at cox.net Sun Jan 27 18:53:03 2013 From: jhphx at cox.net (jhphx) Date: Sun, 27 Jan 2013 18:53:03 -0700 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <510591AB.6030306@crosswire.org> References: <510591AB.6030306@crosswire.org> Message-ID: <5105D9FF.2060906@cox.net> On 1/27/2013 1:44 PM, Troy A. Griffitts wrote: > > Have a go and let me know if you see anything which needs updating > before posting this publicly: > > http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC1.exe > It took me a bit to realize that it didn't install to the directory I had been using. Then I copy and pasted the .exe files into the old one. Otherwise the install looked okey. The Parallel tab for bibles seems to be broke. The texts don't sync correctly. Each text seems to be synced to whatever the tab for that text is set to, not to each other or both to the verse selection tool above. Otherwise I haven't noticed anything else. What were the old issues? Jerry From greg.hellings at gmail.com Mon Jan 28 07:24:32 2013 From: greg.hellings at gmail.com (Greg Hellings) Date: Mon, 28 Jan 2013 08:24:32 -0600 Subject: [sword-devel] Updated SWORD utils Message-ID: The most recent version of the SWORD utilities build for your favorite flavor of Windows can be found at http://dl.thehellings.com/sword-utils/ Download the zip file appropriate to your wants and needs. These should be updated to r2778 and the 32-bit builds should resolve some outstanding issues with ICU detection. Let me know if there is trouble with them. As always, these are built with Xiphos' patch and linked against GLib to properly handle non-ASCII characters in their paths. --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Mon Jan 28 17:07:42 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Tue, 29 Jan 2013 01:07:42 +0100 Subject: [sword-devel] Patches to fix compiler warnings In-Reply-To: <50D3A00E.8060909@ristioja.ee> References: <50D3A00E.8060909@ristioja.ee> Message-ID: <510712CE.7060708@crosswire.org> Jaak, I've partially applied this patch: sword-Wunused-parameter-fix.diff.bz2 I agree that we should safely suppress the warnings in headers for empty virtual methods. These are the hunks I applied. The other warnings in the cpp files should be looked at individually to determine why the parameters are ignored and probably commented before the (void)param. I appreciate you going through all these files. When I was reviewing the patch, it showed me how useful some of these warnings can be. Troy On 12/21/2012 12:32 AM, Jaak Ristioja wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello! > > Please apply these patches (bzip2-ed to workaround sword-devel 90 KB > message size limit and attached) to fix about 3000 compiler warnings > with GCC and Clang. > > The patches should apply to https://crosswire.org/svn/sword/trunk at 2751 > > Blessings, > Jaak > > > PS: Here are the sha1sums: > > 7ba3a0b954b8b545d407eb0f46821e4ebdb1c3bf sword-Wempty-body-fix.diff.bz2 > e47776b086c1d8f686a09114bd162358db18a062 > sword-Wmissing-field-initializers-fix.diff.bz2 > fc68490a4aac0b8954fa02f0832fdccf95573fd7 sword-Wtype-limits-fix.diff.bz2 > eb2749fe94fcb8018be61c8925a12b2503460ac0 > sword-Wunused-parameter-fix.diff.bz2 > 004fbd6ac5bf6107cf37beb4b436f34400ec2774 > sword-comparison-not-assignment-fix.diff.bz2 > df8231f927ae1c34160b57d7b2a90e58a686448f > sword-illegal-source-file-encoding.diff.bz2 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iQgcBAEBAgAGBQJQ05/3AAoJEEqsYmEt1rCON2E//ArXCLZm2Mv0ERKpAoGTvDi+ > JHOOaTf7JW42DkloDiPqMbOSYyLBAbuyJQUp0cFg9pQWTe2TpGu5Fr5n46hsKYSc > FgFTM1fhVqimfeNt74425mxWKG9/DxuXskTI9MXLg6TwN/rVxr8kJpwqrYLnPy9C > 118zyvKCO0YBGAhGx1lkQXmpZbDAvzFszWD9lTHdknDJ/OhMZ12kjmAcpkzraPJ0 > H/KhWGxyGm2mlJ7HuBpKyhVz7oUO7kYBrj9CCBpQwnB17rOCglLqbRLodZIPnd30 > ufL8YjAlwpDvhcIW7CiwaBq23xUjOefReKoAJ6TOw4CQ6AqWvTADj0T/509QoUKg > ZfHBA0vQU0zxI4i67jmt86fI/2X3LuXNBdB9E+0wCLPxgVLuQImw3BufGdupkYe+ > Y3WddcRhtkWh/1yNhxBcB6hZoDZWTWs2iz4pIJYeO40pN6UZKC1MXLoAWqbufMfS > eN0sWDcC7cadq0hkgNLWkWe1fxPfdSwrWgOjICas44elCASBtnjOub9zWhh/HdOB > 668wCQtgBUo0ICdpdNAnsvIQiOhf60sgd99zvwczPeGgJKjvURzK/W4nS9UbwpUE > JESZfeQnLdOWJ2u+THozFLnjoOCw9c5NMZrFhGodVVb/u0bPQzyJ0Z1pT5/BZnOX > 1WC5PuQvGTBx/zepoLAuDLmh+SDqAhVm96fNTvhefY6oq78oQb+aG3N/mq64scXS > S+42S/BJWjDlz21AbfQJprkLOL3DbPBHOxG4/KdF8TFo73iNeTsPfLveumDbn6MS > DUwZETBZdOiGCLuBgmj9GIp/lMmQktdPJHv1JkdoLj+kL23oKR0MdvX5i+4rWOk/ > hs9D8JNCb+0bST71PUIW1HkF3elEYfZO/ciZ0U4mQVFFX/4VzXGJJqf5dh9HhCBZ > 3N1srhXGw4GEEblUv0oT2q+czeSDCjs/zLFQ7ONzbT9qoLOhEbI3cJ89A8hRbSC7 > 3u9OXKjyvJPWQvALxCu90QeS0ygqJPK/JZcHyc7I5J7m61SwhuPU7axKsRTGpHuT > X15w3SwaOz+P+r+WzRPj2OIcihBb4jnf+esk6ows7mNGa3jbm+UsGy/t2i5nb/p+ > DDoSnbxfTTpg9S9KOOrp6mTIZ9voCLXQAkEnx0E/1wu5xTgWI7aSSrXf5eO2JawP > riWTK9EaQ/yUf0SXhVsFKB948ATdoX45ag9OJfR1ShU27qaEE8BBgfGzXjYgcd/o > YujHVNhHfUD1xS8BF4D3G3LoO+l9m4d/iNtnXpc4JPd6f6ZuRGhKiM8V3N7olYYC > 3Xf4hX9V4S2txrPX0XXG5Zq4x90Jx8VxbjN1UKMjTKRgfhghh4c0EzVvpq47sF7z > qtULiOLlbEPUlH78nTu8eZ4Vy1DFhG2BEOSzWZatvO4UxiioewnQtp987ZG7Cpzy > I2RRqrL4vv4FQ2UvOCEqVwYuZTSckcG18Bfy9FjqzH6WW/idBBUzWDrOgcEnke34 > 0A+hQtNo8+WMKD9zBdGEGY8ymNk/lj7F2JAvEhvvdXYemsDBiVfrezCj7EA7ybZp > c8Oisk+EZgo4FMV49ytnjWR1rlsS7wCtLJb1GLjWOggIesrNq8rg9P7j8/u3U/GZ > HDj/UsxInZcZv91u60r8oEl90vdP3hXJxdowKXjRBODFBmfQkJTFYoPd1JIOqyvT > 1eGoYZ/o6ClGbEwcg8XEMOo2MvoF889b/yOOjP6kPt/tQUviwug2McU/KmNThqvU > Arw/+8c/XpW/69SOHIBzgSS1ipcjOafn4k5g8bgkRknx97FaBBQNG9AqYl0iHlMS > LwT9n6gPPBp3lF9LSWlzPvh0+vMQKfH4cwuIQMGwzhd156OkfYmfskoBCDv3VDhh > mhhH502LOleMfoHajzo2IXc2IFToVxZq8rwhWwipXmEoOIH9DpbaaRwgbSjXQr72 > xerD7lzChmTqriH3TmhLXIe5IGpLhPJZOw4AMyuTC3IVvSvMyE4SX/9UHOvxHB3v > sI9OfimIn2NCfsbxLI+0SI8cw7BlSHE63OJjp7yG7oVqbLL7T8VqK5uTgAHWuy16 > HebEXEs5yJtiSh1s2BQX5qxIOs9IFORBtgVlaTFozaVDMk+HMhHSN+pxb49vel0P > ME7AOf1zIxqs1zFeZuqCRRzT8z3UoWcbu5maluSDyyI08i+1nzKDvRMW+77UrAWD > 6sQD+JrHDQoUK8fu3OtUbUaOSyLW5bJ5+MeHEnsPrgvxC+B2lZYw9Bz5QCUSs6xu > FhC7N1OlfM8b+e0EE0IAD2nwTvl0IcJFgbFMEm6KIy2dA6ChoPkTSbi3l0Nm2y7r > iX57mdzKrgcRfUXkFWTrfDx8951qQpw16HNjwCa0zgNbrvKbEFqPzvEPzkNlWw0S > E992keRPJNzpEXe9ZWZUE+qr92CsyqwAvPZ1z1jUT7swIKqrl7/O33CxiK2Iifoc > BRV15T5V8LzWiO0MgOb85UsXZjwSxHMw8theHRAKvqKF0ti8ospgCirEU9ZTv7VF > pSqFVOUBCgWkCtcGE8GaLg7eEleTx5inliILgD6kC+80CV8j1f3L6P2+zLMDxQeo > W/cqdkbk8oL6yoOdRGMXuozPu3g7MQZUDYQplLxGcxYk3fDb2DKgiJw57Rlo+5ji > O7I7wqWI88nEuku0wUIe11ydDSGtYGoOvRC0C4T/Z6vsvd/oNcQAb4tjrjqtKIlY > OdqdFXYt+xF3RepeinW5 > =jSQt > -----END PGP SIGNATURE----- > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From scribe at crosswire.org Mon Jan 28 17:39:39 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Tue, 29 Jan 2013 01:39:39 +0100 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <5105D9FF.2060906@cox.net> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> Message-ID: <51071A4B.8080606@crosswire.org> Thanks David and Jerry for the feedback, The last previously reported bug still outstanding was a problem with the dictionary lookup box. Thanks for the bug report about the parallel view and the options getting reset when changing display preferences. The parallel display was pretty messed up in a few ways. It should be working much better now. The display preferences box should no longer reset all feature display options. Here is a new build: http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC2.exe Thanks for testing the previous version and it would be great if you have a chance to verify your reported problems are fixed. Thank you!!! Troy On 01/28/2013 02:53 AM, jhphx wrote: > On 1/27/2013 1:44 PM, Troy A. Griffitts wrote: >> >> Have a go and let me know if you see anything which needs updating >> before posting this publicly: >> >> http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC1.exe >> > > It took me a bit to realize that it didn't install to the directory I > had been using. Then I copy and pasted the .exe files into the old > one. Otherwise the install looked okey. > > The Parallel tab for bibles seems to be broke. The texts don't sync > correctly. Each text seems to be synced to whatever the tab for that > text is set to, not to each other or both to the verse selection tool > above. > > Otherwise I haven't noticed anything else. What were the old issues? > > Jerry > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From DavidTroidl at aol.com Mon Jan 28 19:03:50 2013 From: DavidTroidl at aol.com (David Troidl) Date: Mon, 28 Jan 2013 21:03:50 -0500 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <51071A4B.8080606@crosswire.org> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> Message-ID: <51072E06.9090809@aol.com> Hi Troy, The Dictionary Lookup is working fine for the Greek, in all the Greek New Testaments, the KJV, even the LXX. In Hebrew it's nothing but gibberish. Whatever I try to look up comes up with a 56xx entry in the Hebrew dictionary. I don't actually remember what the issues were from before. David On 1/28/2013 7:39 PM, Troy A. Griffitts wrote: > Thanks David and Jerry for the feedback, > > The last previously reported bug still outstanding was a problem with > the dictionary lookup box. > Thanks for the bug report about the parallel view and the options > getting reset when changing display preferences. The parallel display > was pretty messed up in a few ways. It should be working much better > now. The display preferences box should no longer reset all feature > display options. Here is a new build: > > http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC2.exe > > Thanks for testing the previous version and it would be great if you > have a chance to verify your reported problems are fixed. > > Thank you!!! > > Troy > > > > On 01/28/2013 02:53 AM, jhphx wrote: >> On 1/27/2013 1:44 PM, Troy A. Griffitts wrote: >>> >>> Have a go and let me know if you see anything which needs updating >>> before posting this publicly: >>> >>> http://crosswire.org/sword/alpha/alpha/sword-win32-1.7.0RC1.exe >>> >> >> It took me a bit to realize that it didn't install to the directory I >> had been using. Then I copy and pasted the .exe files into the old >> one. Otherwise the install looked okey. >> >> The Parallel tab for bibles seems to be broke. The texts don't sync >> correctly. Each text seems to be synced to whatever the tab for that >> text is set to, not to each other or both to the verse selection tool >> above. >> >> Otherwise I haven't noticed anything else. What were the old issues? >> >> Jerry >> >> _______________________________________________ >> sword-devel mailing list: sword-devel at crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From jhphx at cox.net Mon Jan 28 22:43:51 2013 From: jhphx at cox.net (jhphx) Date: Mon, 28 Jan 2013 22:43:51 -0700 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <51072E06.9090809@aol.com> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <51072E06.9090809@aol.com> Message-ID: <51076197.8060900@cox.net> On 1/28/2013 7:03 PM, David Troidl wrote: > Hi Troy, > ... In Hebrew it's nothing but gibberish. Whatever I try to look up > comes up with a 56xx entry in the Hebrew dictionary. David, what Hebrew dictionary are you trying to use? With yesterday's version I had a problem with StrongsGreek but I reinstalled the module and it worked. The Hebrew numbers worked for me. Still do. Jerry From jhphx at cox.net Mon Jan 28 22:50:36 2013 From: jhphx at cox.net (jhphx) Date: Mon, 28 Jan 2013 22:50:36 -0700 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <51071A4B.8080606@crosswire.org> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> Message-ID: <5107632C.7080700@cox.net> On 1/28/2013 5:39 PM, Troy A. Griffitts wrote: > ... Thanks for the bug report about the parallel view ... It seems to be working now. Jerry From dfhmch at googlemail.com Tue Jan 29 02:49:07 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 29 Jan 2013 01:49:07 -0800 (PST) Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <51071A4B.8080606@crosswire.org> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> Message-ID: <1359452947526-4651862.post@n4.nabble.com> Troy, It's so long since I last used BibleCS that a question arises before I contemplate installing it. Does it automatically find the Sword path for all the modules I have installed using Xiphos? e.g. (Win7) C:\Users\David\AppData\Roaming\Sword Is that exactly the same path as used by BibleCS? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651862.html Sent from the SWORD Dev mailing list archive at Nabble.com. From scribe at crosswire.org Tue Jan 29 03:13:48 2013 From: scribe at crosswire.org (Troy A. Griffitts) Date: Tue, 29 Jan 2013 11:13:48 +0100 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <1359452947526-4651862.post@n4.nabble.com> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <1359452947526-4651862.post@n4.nabble.com> Message-ID: <5107A0DC.9050807@crosswire.org> We tried to standardize a location for this a few years back. I added code to the engine at that time and hope everyone is depending on where the engine looks instead of specifying a path themselves. I can tell you that the SWORD engine looks here: $ALLUSERSPROFILE/Application Data/sword/ I have no idea if there is some 'symlink' or something in windows which will resolve this to your path quoted below. One of my major hopes for this release of BibleCS was to get users to migrate modules to where they can be found by other frontends, now that they have other choices. It would be helpful if you could test this in your configuration and let us know what happens. The intent is to share the same SWORD library between applications, Troy On 01/29/2013 10:49 AM, David Haslam wrote: > Troy, > > It's so long since I last used BibleCS that a question arises before I > contemplate installing it. > > Does it automatically find the Sword path for all the modules I have > installed using Xiphos? > > e.g. (Win7) C:\Users\David\AppData\Roaming\Sword > > Is that exactly the same path as used by BibleCS? > > David > > > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651862.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From dfhmch at googlemail.com Tue Jan 29 07:27:20 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 29 Jan 2013 06:27:20 -0800 (PST) Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <5107A0DC.9050807@crosswire.org> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <1359452947526-4651862.post@n4.nabble.com> <5107A0DC.9050807@crosswire.org> Message-ID: <1359469640793-4651864.post@n4.nabble.com> Did we document this in the wiki ? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651864.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dfhmch at googlemail.com Tue Jan 29 07:40:03 2013 From: dfhmch at googlemail.com (David Haslam) Date: Tue, 29 Jan 2013 06:40:03 -0800 (PST) Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <5107A0DC.9050807@crosswire.org> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <1359452947526-4651862.post@n4.nabble.com> <5107A0DC.9050807@crosswire.org> Message-ID: <1359470403342-4651865.post@n4.nabble.com> My Sword library in already shared between Xiphos, xulsword and Bible Desktop. xulsword finds the Sword path automatically. (MK is the same as xulsword) BD has these added manually under Options | Sword Books: C:\Users\David\AppData\Roaming\Sword C:\Users\David\AppData\Roaming\IBT\MK\Profiles\resources The latter is also added manually to Xiphos as a Local Source. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651865.html Sent from the SWORD Dev mailing list archive at Nabble.com. From dmsmith at crosswire.org Tue Jan 29 07:40:36 2013 From: dmsmith at crosswire.org (DM Smith) Date: Tue, 29 Jan 2013 09:40:36 -0500 Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <1359469640793-4651864.post@n4.nabble.com> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <1359452947526-4651862.post@n4.nabble.com> <5107A0DC.9050807@crosswire.org> <1359469640793-4651864.post@n4.nabble.com> Message-ID: I doubt it is there. The location differs between Linux, Windows and Mac. It is not easy to document for Windows as the variable is not on all versions that SWORD/JSword runs on (Bible Desktop still runs on Windows 98). Even when I've tried to explain it to a user, it is confusing. In Him, DM On Jan 29, 2013, at 9:27 AM, David Haslam wrote: > Did we document this in the wiki ? > > David > > > > -- > View this message in context: http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-0RC1-tp4651850p4651864.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From johanma at absa.co.za Wed Jan 30 01:28:47 2013 From: johanma at absa.co.za (Marais, Johan: Absa) Date: Wed, 30 Jan 2013 10:28:47 +0200 Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> References: <1359293196352-4651845.post@n4.nabble.com> <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> Message-ID: <23754FE6FEB4BE41A6909C077FB141B308CEED6AD9@V058MBX001002.ds1.ad.absa.co.za> I am a module developer and trying to use mod2osis and mod2imp ? I am aware that mod2osis is deprecated. I am using the latest utilities, published a few days ago. It seems as if mod2osis and mod2imp run successfully through the bible module, but I cannot find the output. I searched my whole C: drive, but cannot find the output. Please help. Johan From: Troy A. Griffitts [mailto:scribe at crosswire.org] Sent: 27 January 2013 04:13 PM To: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Hello, I need help with the Sword Utilities Well, mod2osis is a reference objective for the filters. Some day the osis2mod + osisosis filter set will perform a well enough to allow a simple module iteration and output to support a lossless round trip using osis2mod and mod2osis. Greg has submitted patches to mod2osis to bring this really close, but to reiterate, the goal for mod2osis is not to produce an export utility, but to be a reference objective to improve the engine's import and filters. So, 'deprecate' is not exactly how I would label mod2osis, but practically for end users, it's the same, Troy David Haslam > wrote: Just a general reminder. mod2osis is a deprecated Sword utility. You can search the sword-devel archives to find out why. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651845.html Sent from the SWORD Dev mailing list archive at Nabble.com. ________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Important Notice: Absa is an Authorised Financial Services Provider and Registered Credit Provider, registration number: NCRCP7. This e-mail and any files transmitted with it may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Absa. Any views or opinions presented are solely those of the author and do not necessarily represent those of Absa. This e-mail is subject to terms available at the following link: http://www.absa.co.za/disclaimer. The Disclaimer forms part of the content of this email. If you are unable to access the Disclaimer, send a blank e-mail to disclaimer at absa.co.za and we will send you a copy of the Disclaimer. By messaging with Absa you consent to the foregoing. By emailing Absa you consent to the terms herein. This email may relate to or be sent from other members of the Absa Group. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfhmch at googlemail.com Wed Jan 30 01:41:03 2013 From: dfhmch at googlemail.com (David Haslam) Date: Wed, 30 Jan 2013 00:41:03 -0800 (PST) Subject: [sword-devel] Hello, I need help with the Sword Utilities In-Reply-To: <23754FE6FEB4BE41A6909C077FB141B308CEED6AD9@V058MBX001002.ds1.ad.absa.co.za> References: <1359293196352-4651845.post@n4.nabble.com> <6474b68f-5417-42ba-a436-ec480b9d4653@email.android.com> <23754FE6FEB4BE41A6909C077FB141B308CEED6AD9@V058MBX001002.ds1.ad.absa.co.za> Message-ID: <1359535263316-4651868.post@n4.nabble.com> They both send the output to stdout. See https://en.wikipedia.org/wiki/Standard_out#Standard_output_.28stdout.29 You need to send the output to a file, using the normal methods in Windows (like in Unix). Here's how I use mod2imp. First create a folder where you want the output file... The command line assumes that my Sword path has a symbolic link (e.g. utils64) made for where the Sword utilities were stored after downloading and extracting. utils64\mod2imp HinERV >Export\HinERV\HinERV.raw.imp.txt This command line assumes that you are in a command shell with the Sword path as the current directory. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651868.html Sent from the SWORD Dev mailing list archive at Nabble.com. From davidtroidl at aol.com Wed Jan 30 16:06:04 2013 From: davidtroidl at aol.com (davidtroidl at aol.com) Date: Wed, 30 Jan 2013 18:06:04 -0500 (EST) Subject: [sword-devel] BibleCS 1.7.0RC1 In-Reply-To: <51076197.8060900@cox.net> References: <510591AB.6030306@crosswire.org> <5105D9FF.2060906@cox.net> <51071A4B.8080606@crosswire.org> <51072E06.9090809@aol.com> <51076197.8060900@cox.net> Message-ID: <8CFCD558361FA5D-62C-53B42@webmail-m050.sysops.aol.com> Hi Jerry, Sorry, I haven't had time to get back to this. Though I did install the RC on my desktop, where the Hebrew dictionary lookup works fine. I have actual Hebrew words, too. On the laptop, I was getting ANSI/Unicode mismatch combining characters. I'll have to check the modules. David -----Original Message----- From: jhphx To: SWORD Developers' Collaboration Forum Sent: Tue, Jan 29, 2013 12:46 am Subject: Re: [sword-devel] BibleCS 1.7.0RC1 On 1/28/2013 7:03 PM, David Troidl wrote: > Hi Troy, > ... In Hebrew it's nothing but gibberish. Whatever I try to look up > comes up with a 56xx entry in the Hebrew dictionary. David, what Hebrew dictionary are you trying to use? With yesterday's version I had a problem with StrongsGreek but I reinstalled the module and it worked. The Hebrew numbers worked for me. Still do. Jerry _______________________________________________ sword-devel mailing list: sword-devel at crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page -------------- next part -------------- An HTML attachment was scrubbed... URL: From gary.holmlund at gmail.com Wed Jan 30 18:46:14 2013 From: gary.holmlund at gmail.com (Gary Holmlund) Date: Wed, 30 Jan 2013 17:46:14 -0800 Subject: [sword-devel] Sword API-151 bug patch In-Reply-To: <50D88A28.2040402@gmail.com> References: <50D88A28.2040402@gmail.com> Message-ID: <5109CCE6.7090403@gmail.com> On 12/24/2012 09:00 AM, Gary Holmlund wrote: > I have attached a small patch to the Sword API-151 bug. I would > appreciate someone looking at it and applying it. > > This problem is affecting indexing in BibleTime with certain modules. > In the example I gave, part of the HunKar module before Malachi can't > be searched. > > Thanks, > > Gary Holmlund I am sending a gentle reminder about this defect. We have had another person run into this today. I have solved it and supplied a patch (a 1 character change). I would like to see it fixed before a sword 1.7 release. Gary From niccarter at mac.com Thu Jan 31 20:13:16 2013 From: niccarter at mac.com (Nic Carter) Date: Fri, 01 Feb 2013 14:13:16 +1100 Subject: [sword-devel] Personal Commentary & av11n Message-ID: Heya team :) So, I'm wondering how various front-ends are going with av11n stuff and personal notes/commentaries/journals? As some of you know, PocketSword still doesn't have note taking as a feature, but it's something I'm looking at adding... :) But if a user has notes for a certain Bible in English, how does that work with a Bible in Spanish? [this shouldn't matter, as it should instead be a v11n thing] And if they switch Bibles from a KJV v11n one to, say, an NSRV v11n one, what happens? And what is expected to happen? And does this vary depending on whether the front-end uses the "Personal Commentary" module or another method for note-taking? Anyway, asking these questions before I'm ready to be implementing it so I can try to decide what the best approach will be! :) Thanks heaps, ybic nic... :) ---- Nic Carter PocketSword Developer - an iOS Bible Study app Twitter: http://twitter.com/pocketsword iTunes: http://itunes.apple.com/app/Pocketsword/id341046078 From bogus@does.not.exist.com Wed Jan 16 06:18:08 2013 From: bogus@does.not.exist.com () Date: Wed, 16 Jan 2013 13:18:08 -0000 Subject: No subject Message-ID: buf.appendFormatted("
<%s>", from buf.appendFormatted("<%s>", Similar stuff is done for the morph's links. Also for the showNote stuff (line 256) I have similarly removed the & tags. :P buf.appendFormatted("*%c%s", Oh, plus I went ahead and added support for OSIS underline stuff to osishtmlhref.cpp if you're interested in incorporating that back into SVN? I actually have it on my todo list to send a diff for it and some tweaks to stringmgr.cpp, but if you take a look at https://bitbucket.org/niccarter/pocketsword/src/70a056c42a45a2babe5bffbd3859596aeade867c/externals/sword/src/modules/filters/osishtmlhref.cpp?at=default you can decide what you want to pull across yourself rather than I send a patch just for the underline stuff? Does that help? [aside: I took a raw dump of the HTML thrown out by the filter and tried to validate it as html. I started cleaning up what was produced (by an OSIS module) and then gave up. But that is why I have the "&" stuff in there, as that is what it "should" be.] > > Bibletime, same. I know you guys have had stuff styled for quite some time. > > Would ultimately like to get this filter set to something we all can share and improve. > > Troy > > > > _______________________________________________ > sword-devel mailing list: sword-devel at crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page From jamie at critos.co.uk Sat Jan 12 02:31:02 2013 From: jamie at critos.co.uk (ARA Jamieson) Date: Sat, 12 Jan 2013 09:31:02 -0000 Subject: [sword-devel] Generating / displaying Sword Message-ID: <21BA69F4CDAE4C4FB34D69F7FDC73176@Makyra1> I'm a newbie with OSIS / Sword, so apologies if this is a dumb question or I'm posting it to the wrong place. I'm currently converting USX to OSIS using my own processing, then using osis2mod.pl to generate Sword, and then displaying the results using Xiphos on PC. As a test, before I start with non-English language texts, I'm working with a copy of the King James Version, since it makes it easier to see what's going on. The first few hundred characters of the OSIS appear below :-
Matthew_B
Matthew_C
Matthew_D
The Gospel According to St. Matthew

The book of the generation of Jesus Christ, the son of David, the son of Abraham. Abraham begat Isaac ... (I've hacked this manually a bit, because I needed to distinguish the various occurrences of "Matthew" in the output to help me understand what was coming from where.) I thought this was in line with the OSIS spec, but maybe it isn't, because Xiphos isn't display what I might have expected / hoped for - at least when it comes to chapter headings and titles ... 1. "Chapter 1", along with the "1" for verse 1, come out before any of the headings. 2. I'm seeing an awful lot of headings - Matthew_B, Matthew_C, Matthew_D and "The Gospel ...". I assume this means I'm generating too many "title" tags, but I'm not sure which of these I can safely get rid of. 3. I'd assumed that the "tableOfContents" tag was used to mark the place in the text to which a table of contents should point. Is this correct? If so, clearly I'm using it wrongly, because Matthew_C is being displayed rather than simply being used internally to sort out the linkage. 4. I'm wondering about the fact that I have two

s. The first of these is there because we genuinely are at the start of a book. The second arises because the USX / USFM contains an \mt tag, and I'm interpreting section Appendix F of the OSIS manual as saying that's what's needed; but perhaps I've got that wrong. Any comments would be very gratefully received. ARA "Jamie" Jamieson -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 1391666 bytes Desc: not available URL: From jbarnesweb at yahoo.com Tue Jan 22 22:38:48 2013 From: jbarnesweb at yahoo.com (Jeff Barnes) Date: Wed, 23 Jan 2013 05:38:48 -0000 Subject: [sword-devel] bindings/objc build broken Message-ID: <1358919293.68943.YahooMailNeo@web160701.mail.bf1.yahoo.com> Did a fresh checkout of?https://crosswire.org/svn/sword/trunk. Changed to bindings/objc. 1) The bindings/objc/README instructions are inaccurate. There is no Makefile in build_sword. 2) The build breaks in build_sword/build_mac_sword.sh. $ cd build_clucene $ make release-fat ... looks like successful build for 3 platforms $ cd ../build_sword $?./build_mac_sword.sh -a fat -c ... ./configure: line 15671: syntax error near unexpected token `CLUCENE2,' ./configure: line 15671: `PKG_CHECK_MODULES(CLUCENE2, libclucene-core >= 2.3,,true)' $?pkg-config --cflags --libs libclucene-core -I/usr/local/include -I/usr/local/include/CLucene/ext ?-L/usr/local/lib/ -lclucene-core $?which pkg-config /usr/bin/pkg-config ??System Version:Mac OS X 10.6.8 (10K549) ... ??Model Name:MacBook Pro ? Model Identifier:MacBookPro6,2 ? Processor Name:Intel Core i5 ? Any help appreciated. Jeff From stefan-husmann at t-online.de Sun Jan 13 05:16:24 2013 From: stefan-husmann at t-online.de (Stefan Husmann) Date: Sun, 13 Jan 2013 12:16:24 -0000 Subject: [sword-devel] automake issue under Arch Linux Message-ID: <50F2A4AC.3060309@t-online.de> Hello, this is my first post here, and if it has been brought up already -- I only searched in January and december's mail archives --, I apologize. I am buildng the sword library from the svn sources and have had problems with aclocal coming with automake 1.13.1. The simple patch at http://paste.pound-python.org/show/29082/ solves this. Please consider it. Best Regards Stefan Husmann