Re: [sword-devel] CrossWire repos?

[TS]

My impressions from this thread is that this is still an unresolved
server issue? If the new server was changed to be exactly like the old
server, then PocketSword should be able to download, correct? This
workaround is good and all, but it's still a workaround, which is to
say, a temporary fix.

p.s. - I didn't realize how much of this thread was about PocketSword.
Previously, based on the title and the snatches of the conversation that
crossed my eyes, my impression was that this conversation was mostly
about a server matter. I would have replied sooner regarding PocketSword
if I had known.

-TS

On 3/16/2019 1:17 AM, David Haslam wrote:

I can add that for most older modules and some newer modules, the workaround 
also succeeds for installing the module search index automatically from our 
server.

That’s because the indices are stored in a particular server directory whose 
path does not depend on the module download path or access protocol.

However, there are still several CrossWire modules for which the search index 
was never created when the module was either first released or last updated.

One example: Middle English : Wycliffe

These omissions should and could be rectified by the “Modules Team”.
Let’s make it a better experience for PocketSword users.

Best regards,

David

Sent from ProtonMail Mobile

On Sat, Mar 16, 2019 at 07:47, David Haslam  wrote:


Workaround for PocketSword module downloads from CrossWire.

Add FTP Source

This is one of the hidden options under the folder icon at top right.

Set up as the greyed out example.

Just tested successfully.

Praise the Lord !

Best regards,

David Haslam

Sent from ProtonMail Mobile

On Mon, Mar 11, 2019 at 20:05, Troy A. Griffitts  wrote:


Thanks for the feedback.  When I get time, I'll try to expand the test 
application to not simply perform a directory listing, but to actually try to 
install a module via the CURLHTTPTransport driver.

On 3/11/19 11:38 AM, Johan Marais wrote:


Troy,

I tried downloading 2 English bibles from CrossWire into PocketSword, but still 
the same, it took about 1 second to download and install, but nothing was 
installed.

Best regards,

Johan Marais

On 11 Mar 2019, at 20:17, Troy A. Griffitts  wrote:


I have checked the configuration of both servers and made the IndexOptions 
align exactly.  I didn't notice much of a change, but could someone please 
check if they can install modules from CrossWire now?

I have also added a new test program which is not included in the build of 
standard test programs, but is available if anyone would like to look more 
deeply into the issue

http://crosswire.org/svn/sword/trunk/tests/httptest.cpp

For the record, I created the test program after aligning the IndexOptions on 
the server didn't appear to me to make much difference (e.g., the date format 
was still the same), with the intent to debug the problem, but both URLs in the 
test program parsed directory listings just fine...  So... Either, something in 
the IndexOptions did indeed make a minor adjustment to the output which fixed 
the problem, or else the problem is something entirely different.

Jaak,

Yeah, of course we could create a generated index.html file for each folder and 
this would assure we could read the contents, but a goal is to keep deployment 
of these repositories easy for module publishers and http directory listings is 
only used by PocketSword.  Thanks for the suggestion.

Troy

On 3/8/19 12:08 AM, David Haslam wrote:


Thanks Troy,

Who’d have thought that a date format would be so critical ?
It’s often the little things that catch us.

Nic Carter has replied off list.
He’s the pumpkin holder for PS.

Aside: Does any other SWORD front-end use the same parsing code?

When the new Apache server was configured, did we have a choice about the date 
format?

Can a server setting be changed?
Would that in effect mend the PS module installer?
Without requiring any immediate work on PS.
(And without breaking anything else)

Finally, PS needs serious work to successfully recompile against iOS 12.1.x
It’s a long time since the last PS release!

Best regards,

David

Sent from ProtonMail Mobile

On Fri, Mar 8, 2019 at 01:20, Troy A. Griffitts  wrote:


So, here's my guess.  Nic uses HTTP instead of FTP to read our distro and does 
some magic to parse Apache httpd directory listings.  Here's our old server and 
here's our new (as DM sent previously).  There are some slight differences 
(notice the date format, at lease).

old: https://guest.crosswire.org/ftpmirror/pub/sword/raw
new: https://ftp.crosswire.org/ftpmirror/pub/sword/raw

The parsing code is here:

http://crosswire.org/svn/sword/trunk/src/mgr/curlhttpt.cpp

Who owns PocketSword these days?

Troy

On 3/7/19 1:18 PM, DM Smith wrote:


The URL that PocketSword uses https://ftp.crosswire.org/ftpmirror/pub/sword/raw 
has no problems.

DM


On Mar 6, 2019, at 1:34 PM, David Haslam  wrote:

Did DM find out anything?

David

Sent from ProtonMail

[sword-devel] Question about backwards compatibility and search index download-ability, especially in relation to low-cost, low-power computers (such as might be in developing countries?)

[TS]

Hi,

 To put it simply, I was wondering what is Crosswire's or perhaps 
Troy's position on backwards compatibility. I thought that the desired 
goal, if possible, was for Sword to be able to run on as many devices as 
possible. However, recently I've seen in mailing list postings or emails 
that perhaps I was mistaken? It's also occurred to me that perhaps my 
impression is with regards to the Sword engine only and that this does 
not include front-end backwards compatibility? So, I'd appreciate some 
clarity on the matter.
 In specific, I'm asking this question because in the past, I know 
that organizations have made projects to create simple, low-cost 
computers (such as OLPC). I know that the first gen OLPC was made around 
the same time as the first iPhone and had roughly similar specs (if I'm 
interpreting the specs correctly). It was the size of a small laptop, 
but did not have enough processing power to play videos. This type of 
computer was created for developing countries. So, if computers such as 
these exist enough, then it also seems to me that they may have problems 
generating search indexes the same way that the first iPhone did. 
Therefore, I'm wondering if perhaps there is still a good reason for the 
search indexes to be downloadable?
 On the other hand, David's post back in Feb. 16,2019, titled 
"[sword-devel] ParaTExt Lite (Android OS)", contained a link to an 
article about the development of ParaText Lite. This article seemed to 
suggest that smartphones have penetrated even the most remote of places. 
So, it makes me wonder if the situation of people (such as those in 
developing countries) being stuck with old computers is perhaps not very 
large? I guess I don't know either way, but since nobody here (I think?) 
has brought it up and it would possibly be impacted by search indexes 
download-ability, this all seems like something worthwhile to ask/talk 
about.
 (Btw, it seems to me that Android would probably be the dominant 
smartphone OS. I don't want to derail this post explaining "why", so it 
may be sufficient enough to mention that ParaText Lite was only made for 
Android OS.)
    (Also, the current gen laptop of OLPC does have enough power, I 
think. I would also imagine that the current Raspberry Pi computers have 
enough power as well.)


-TS

--
- Timothy


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Search error in PocketSword for ancient Greek text

[TS]

Hi,
 In the past, when I have tried searching Greek text in PocketSword, it 
causes an error. I seem to recall, that it went something like this. If I put 
the full Greek word in, it won't find the word, but if I enter part of the 
Greek letters of a word in, then it will find the word. It seems to, for some 
reason, not like the Greek "s" suffix. I think, it may even be possible for me 
to enter a word and only leave out the last Greek character "s", and it can 
find the word. But if I add the "s", then it cannot find the word. Quite a lot 
of Greek words, by the way, end with an "s".
 I have searched Old Testament Greek text this way. Such as the Septuagint 
(LXX). It was in order to see how certain Hebrew words/concepts translate into 
Greek. And perhaps vice a versa. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Does the CLucene indexing work for non-English texts?

[TS]

Does the CLucene indexing work for non-English texts?

David's recent question about languages without spaces caused me to be a bit 
curious about this matter. Briefly looking at the current Apache Lucene code, 
their appears to be extra code for non-English text. However, this is in 
comparison to the Clucene code for PocketSword. And I seem to recall that, in 
general, the CLucene code in PocketSword may only be for reading indices and 
not for writing them. Also, to clarify  further, it is possible that an index 
is created, but with errors?
 For example, when I search Koine Greek texts, it does so erroneously. I 
think that I'll start a separate post regarding the Greek search and indexing 
in specific. 
 
-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Bishop for Android and iOS / JavaScript bindings

[TS]

Hi,
 It looks interesting. I'm curious to try it. What should I do if I want to 
keep updated on the ongoings of this? You mentioned that everyone knows that 
Cordova bindings have been getting worked on, but I don't recall offhand seeing 
stuff being posted about it. I'm not familiar with Cordova so maybe stuff was 
posted  and I didn't realize it? Or, is there a different mailing list or 
something for it?

-TS

--Sent from phone--

> On Feb 28, 2018, at 6:26 PM, Troy A. Griffitts <scr...@crosswire.org> wrote:
> 
> Dear team,
> 
> You all know we've been working on Cordova bindings for SWORD for quite some 
> time now.  We now have a simple reader written in JavaScript which will run 
> unchanged on both Android and iOS.Bishop includes an InstallMgr to 
> auto-discover remote installation sources and let a user install SWORD 
> content.
> 
> I've kept the development code name "Bishop", my favorite android (from 
> Aliens) and almost appropriate for a Bible app :)  I've also tacked on our 
> boring moniker from our Windows app, "Bishop: The SWORD Project for Android". 
>  Long name but should get more search hits.
> 
> Basically, Bishop's UI has 2 basic modes:
> Reader: which simply shows 1 chapter of up to 3 Bibles in parallel.
> Verse Study: When in reader mode, as the user scrolls, one verse will always 
> be active, when "Verse Study" is chosen from the menu, the user can then 
> drill down into that active verse.  Verse Study has 4 tools:
> Word Study: shows the verse broken down word by word, showing the original 
> Greek or Hebrew behind each word, along with a simple definition.
> Commentary: shows all installed commentary for that verse.
> Witness Study: shows all available ancient New Testament manuscript witnesses 
> which attest to the current verse.
> Variant Study: shows all variant between the manuscript witnesses for the 
> current verse.
> Other features include very basic bookmarks and search.  The Android 
> release has an initial attempt at BibleSync support to send your current 
> verse out to all your friends running Bishop on the same network (thanks 
> Karl!).
> 
> The initial goal of Bishop was to be the thinnest client on top of the 
> bindings, as an example and thus uses no 3rd party libraries, save jQuery.  
> Now that the initial release is completed and can serve as an example, we're 
> free to improve the mobile user interface if anyone feels called to join the 
> team and give it a shot.
> 
> Installation locations follow.  It's best to let Bishop install its basic set 
> of SWORD modules upon first run, so it has a minimal set of tools it can use 
> to operate.  It will prompt you to do this when you first launch the 
> application and it finds no modules installed.
> 
> Android users can install the app from:
> https://play.google.com/store/apps/details?id=org.crosswire.bishop
> 
> iPhone users will need to send me their UDID for testing while we try to get 
> through the Apple Store approval process.  I haven't even tried yet as I 
> don't have much hope that it is "pretty" enough for them, but the download 
> link for the iPhone binary is here:
> 
> https://crosswire.org/bishop/manifest.plist
> 
> https://crosswire.org/bishop.ipa
> 
> The code can be had from:
> 
> http://git.crosswire.org/main/bishop
> 
> Please let us know what you think if you are a user, and offer your 
> suggestions from a usability perspective.
> 
> If you are a developer, please offer comments and suggest features you have a 
> desire and are willing to add.
> 
> Please give us a great rating so we show up in a search in the Play Store and 
> let others know.  I think we have some unique feature that other app don't 
> offer and I've been using Bishop as my morning reader for a while now.  The 
> default fullscreen text without clutter is pleasant. 
> Christ's best for you!
> 
> Troy
> 
> 
> ___
> sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NASB

[TS]

Hi, I know that this post is old, but I believe that I need to clarify 
something(s).



 At the very beginning of my earlier email (below with Greg's replies), when I was 
writing about Kahunapule's posts, I just meant his posts about the NASB in specific being 
ignored. I was not meaning to refer to all his posts in general which seems to be how my 
wording was taken. Also, I believe that some time later an email was sent out (by the 
admin of the mailing list I think?) letting everyone know that the mailing list server 
had some issues during this period of time. So, perhaps this may be related as well to 
the confusion. At any rate though, I am sorry and do apologize to Greg Hellings and, if 
needed, to Kahunapule Michael Johnson for any offenses. None was meant. Greg's reply to 
what I had written regarding Kahunapule's posts came across to me as a strong rebuttal 
and defense, but also a misunderstanding. I think that I originally did not think that 
the misunderstanding was worth replying to, but over time it has come to weigh on me. 
Perhaps I'm being overly sensitive in this, but I do believe in honesty with others and 
trying to be "at peace with others" as much as one can. So, it seemed good that 
I should write this.



Sincerely,

TS


On Feb 24, 2017, at 01:47 PM, Greg Hellings <greg.helli...@gmail.com> wrote:






On Fri, Feb 24, 2017 at 3:22 PM, TS <outofthec...@icloud.com> wrote:


From what I can tell, a member named Kahunapule Michael Johnson seems to be 
able to already create a NASB Sword module.


This is according to his post here and from last year as well.
http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html

I don’t quite understand why his posts keep getting ignored.



Kahunapule's posts are not ignored. Many of his are informative, rather than 
asking for response or help. But he is not ignored. For instance, he wasn't 
really looking for help in setting up his automated repository of modules - he 
was keeping the community apprised of his progress on it. And people have given 
him responses and feedback when appropriate.
 


He seems to have been in contact with the Lockman Foundation, but for some 
reason thinks or thought that the NASB Sword module would be for free.

From what I understand from the forum discussions, in order for the NASB Sword 
module to be released, it would have to be a commercial module. Part of this 
means that it would obtainable through paying for it. So, the Lockman 
Foundation or Crosswire or some other entity would then host it on their 
website which allow for it to be downloaded only after paying for it. I’m 
guessing that a password would be provided to unlock the module.



It would not be sold by Crosswire. Crosswire is a non-income entity and does 
not sell any materials.
 


Can anyone tell me why Johnson's work is not being used? Generally speaking, 
could not Michael send it to Greg, Greg review it, and then if it passes, it be 
acceptable for release?



The goal was for us to be able to hand to Lockman, not a completed module, but 
a piece of software that they could feed their existing module through any time 
it changed and they could produce an updated version of the module themselves 
directly for distribution. So Kahunapule's work would not satisfy that 
requirement, unless he was starting from Lockman's internal text.
 


In addition to this, Greg himself already seems to have the work done in order 
to create the module. It seems that the real question is, does it work with all 
the major SWORD/JSword frontends? DM Smith confirmed last year that it worked 
with JSword and released a beta of BibleDesktop which supported it as well. The 
only two problems left (it possibly seems at least) based on DM Smith’s email 
are:

1) Does the Sword engine support having the lex as a single module (which is 
apparently a requirement from the Lockman foundation)? This would mean, for 
example, that Strong’s would have “G” (Greek) and “H” (Hebrew”) both as “keys”. 
(I’m guessing having more than one key is the problem or the order of the keys 
is? Would having them in the same module be a problem? Would having two 
different keys be a problem or would the order of “G” and then “H” be a 
problem?)



I don't know if the engine supports this. It's a worthy question.



2) Does the text display the same on BibleDesktop, SwordWeb and The SWORD 
Project for Windows? Apparently there’s a word which is accented differently?



There is a third item, and that is one of the bigger problems - there is more 
than just the NASB in the module set originally provided by Lockman. Troy 
requires that all of the modules build equally well off of the same codebase in 
an automated fashion. I ran into an issue with one of the modules that 
introduces a character set not present in the NASB. One of the characters in 
the set is represented the same way as a portion of the NASB markup but with 
very different semanti

Re: [sword-devel] PocketSword beta testing

[TS]

Hi,
So, yesterday I took a look at Nic’s new code and compared it to the 
last code that I had worked on which turned out to be back in Dec. It seems 
that a lot of our code may be complimentary to each other!  :)  So, this is 
good news. I need to dig in some more, but it looks like we focused on 
different parts of the code. The majority of differences that I saw was that I 
1)  focused on the Sword engine being more 64 bit compliant, so I have a more 
recent version of the Sword engine which is more 64 bit compliant (which makes 
Xcode happier). And 2) also, it looks like I focused more on fixing the search 
downloader using Apple’s newer API. Apple deprecated the class NSURLConnection 
which is what PocketSword normally used to download modules from servers. You 
can see here:

https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/WorkingWithHTTPAndHTTPSRequests/WorkingWithHTTPAndHTTPSRequests.html

Here’s the part in specific from the website:
"If you just need to retrieve the contents of a URL and do something with the 
results at the end, in OS X v10.9 and later or iOS 7 and later, you should use 
the NSURLSession <https://developer.apple.com/reference/foundation/urlsession> 
class. You can also use the NSURLConnection 
<https://developer.apple.com/reference/foundation/nsurlconnection> class for 
compatibility with earlier versions of OS X and iOS."

So, I added/modified a lot of code using NSURLSession. The file 
PSIndexController in specific has most of these changes. The text of the file 
is now a lot longer since the NSURLConnection class involved a lot of 
methods/functions and the newer version NSURLSession sorta has equivalents. 
Also, offhand I believe that Apple’s new API and maybe one of the libraries 
being used changed how threading was done as well. PocketSword normally 
downloads modules on the main thread and I seem to recall that it can not be 
done that way any more. So, I had to write a lot of new code to manage the 
threads so that the downloads don’t download on the main thread anymore. I’m 
guessing that this was done so that long downloads could not block the main 
thread and effectively cause an app to get stuck on a download window. Then I 
had to do some adjusting so that the MBProgressHUD would work right and show a 
progress display to the user.

So, what this means is that normally PocketSword would stay on the download 
window while downloading whereas now, the user can actually go back to a 
different screen during the download. That’s what happened during my testing at 
least which makes sense since the main thread isn’t doing the download. More 
work needs to be done though since it’s right now not very clear to the user 
that the download is happening “in the background”.

It seems that Nic focused mostly on code specific to PocketSword. A lot 
of 64 bit changes that I had no idea that they needed to be done as well as 
some other specific iOS code that I didn’t know needed updating.

Regarding my code though, there currently is a problem. I only got far 
enough to code and do some testing for the newer API. I didn’t get far enough 
to code and test for backwards compatibility. :(Offhand, I think it just 
requires code to be written in the PSIndexController file to test for which 
version of iOS is being used and then for it to use the right methods/functions 
accordingly. The code for showing the download progress might need adjustments 
too accordingly. I’m going to try working on the code this week to see about 
the backwards compatibility and to try getting it going.

The code that I mentioned that I last worked on back in Dec. that I’m 
using for comparison I’ll upload to my account on bitbucket so that Nic and/or 
whoever can take a look at it. Also, just a note, one of the reasons why my 
code in the past wasn’t put into Nic’s repo was because when I joined 
Bitbucket, they seemed to be going through a major overhaul of their software 
and their instructions didn’t match anymore to the software. So, between that 
and other things going on in life, it just became easiest to just do an upload 
to my own account as opposed to troubleshooting and trying to figure out how 
their software was suppose to work. I am curious though about how the merging 
process is suppose to work so I do plan to learn about it.

In side news, I  think I also ran across a problem with “find all” for 
Strong’s numbers and fixed that.


-TS


> On Apr 22, 2017, at 6:54 AM, Nic Carter <niccar...@mac.com> wrote:
> 
> Hi all,
> 
> So, I have tried to play around with PS to get it happy with all the hoops it 
> needs to jump through for it to work again on iOS. This incorporates some 
> hard work done by Manfred & TS.
> 
> Changes:
> - enhancement: 64-bit
> - FIX: search downloader (??)
> - FIX: “fin

[sword-devel] "Search" related problems with regards to accent/diacritic marks in the Hebrew OSHB and WLC

[TS]

I was curious to see if I could use the accent/diacritic marks to my advantage 
to find words with the same markings. I used PocketSword. Clucene is the search 
engine it uses. When I have all the markings turned on in OSHB, copy a word, 
and then try and find the word, I get zero results. If I turn them all off and 
do the same thing, it'll also fail if I have fuzzy search enabled. Since the 
word I chose seemed to have a vowel point on the Shin character (despite the 
markings being turned off) I chose a different word without any markings. 
Searching with that word copied and pasted in kept giving me the same two 
results despite changing different search settings. The verse that I copied it 
from did not appear in the results either. It seemed to only find occurrences 
of the Hebrew word when there was a footnote link right next to the word. 

 With  WLC module: Tried different combinations of fuzzy search, all words, or 
exact phrase and none would give me results from a word with its 
accent/diacritic marks in the text with them. With the marks turned off, with 
fuzzy search set to off and using the  "all words" setting, this does work or 
at least I get results, but I don't offhand know if it's finding all the words 
that it should. If I do the same using a different word without a leftover Shin 
point, then I get zero results no matter what I set it to. In the other module 
I seem to get results which had a footnote link next to them, but I guess this 
module doesn't have footnotes and so nothing was found?

In specific, I had the app opened at Is. 61:1. The words that I used, in order 
were:
לְבַשֵּׂ֣ר
לבשׂר
 ענוים

Do any other frontends have this problem?

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Hebrew OSHB and WLC Bible modules do not fully remove all accenting/diacritics when those settings are turned off?

[TS]

I have this problem when using PocketSword. The Aleppo module seems correct 
though. Does anybody else have this problem with any other frontends ? 


For example, as I understand it, Is. 61:1 should not contain any vowel points 
above the ש "Shin" letters. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] How does the "diatheke" front end have search abilities? Is it using CLucene?

[TS]

Hi, my impression from the wiki page describing "diatheke" was that it's a CLI 
to the Sword engine. Due to recent mailing list discussion, it's occurred to me 
that I do not understand how it has search abilities due to CLucene (or ?) not 
being part of the core Sword engine. If diatheke was written to allow for it to 
be able to use CLucene or etc., that sorta makes sense to me, but I'm getting 
the impression from the discussion that maybe it's not using CLucene? 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] NASB

[TS]

From what I can tell, a member named Kahunapule Michael Johnson seems to be 
able to already create a NASB Sword module. 

This is according to his post here and from last year as well.
http://www.crosswire.org/pipermail/sword-devel/2017-January/044041.html

I don’t quite understand why his posts keep getting ignored.

He seems to have been in contact with the Lockman Foundation, but for some 
reason thinks or thought that the NASB Sword module would be for free.

From what I understand from the forum discussions, in order for the NASB Sword 
module to be released, it would have to be a commercial module. Part of this 
means that it would obtainable through paying for it. So, the Lockman 
Foundation or Crosswire or some other entity would then host it on their 
website which allow for it to be downloaded only after paying for it. I’m 
guessing that a password would be provided to unlock the module.

Can anyone tell me why Johnson's work is not being used? Generally speaking, 
could not Michael send it to Greg, Greg review it, and then if it passes, it be 
acceptable for release?

In addition to this, Greg himself already seems to have the work done in order 
to create the module. It seems that the real question is, does it work with all 
the major SWORD/JSword frontends? DM Smith confirmed last year that it worked 
with JSword and released a beta of BibleDesktop which supported it as well. The 
only two problems left (it possibly seems at least) based on DM Smith’s email 
are:

1) Does the Sword engine support having the lex as a single module (which is 
apparently a requirement from the Lockman foundation)? This would mean, for 
example, that Strong’s would have “G” (Greek) and “H” (Hebrew”) both as “keys”. 
(I’m guessing having more than one key is the problem or the order of the keys 
is? Would having them in the same module be a problem? Would having two 
different keys be a problem or would the order of “G” and then “H” be a 
problem?)

2) Does the text display the same on BibleDesktop, SwordWeb and The SWORD 
Project for Windows? Apparently there’s a word which is accented differently?

The writing on the mailing list regarding the NASB is quite convoluted. I think 
it’s important though for Matt Zabojnik to know that it’s possible that he 
doesn’t need to make a new module. He may instead be able to just coordinate 
and or facilitate things between Greg and Kahunapule Michael Johnson as I wrote 
above. They both have working modules from what I can tell.

I also do apologize if I’m offending or mis-representing anyone. I’m trying to 
distill the current situation of the NASB Sword module into its essentials.

-TS

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] PocketSword can speak!

[TS]

:)
I'm glad to see that I'm not alone in enjoying this type of feature. I 
actually have a story regarding this matter that I hope to write about 
later.


How exactly are you triggering the TTS to work? There's two 
different methods that I know of at least. You can have the "Screen" 
read or you can select the text (or use the pop up menu to select all of 
the text) and then choose from the pop up menu "Speak".


Strangely enough, even though the same voice is used both ways, the 
quality is not the same. The Screen reader version, for example, will 
pronounce the "L" in "LORD" as a separate word and then "ORD" as the 
following word whereas selecting the words themselves and having them 
spoken will not have that problem. The screen reading version also 
sounds more stilted.


As far as I can tell, only one chapter at best will be read either 
way. This is, for me, is somewhat limiting as I would want the reading 
to continue going chapter after chapter. "And-bible" (the JSword based 
front-end which runs on Android) also has text to speech ability and 
it's pretty amazing on that app. The ability for the text to be read is 
integrated into its User Interface. So, it's very easy to see and use. I 
believe that it will also move on to the next chapter and continue 
reading out loud instead of stopping at the end of a chapter. It's a 
feature that I sorta wish that PocketSword had.


Also, to emphasize something that you touched on, "English" is not 
the only "language" in which the text to speech works with on the 
iPhone. For example, if you use a Chinese Bible, it can read it out loud 
in Chinese. Or, if you select to use the Hebrew Aleppo Codex (Old 
Testament in Hebrew), you can also have it read the text out loud to you 
in Hebrew. (There's 3 dialects of Chinese available by default on the 
iPhone and one of Hebrew as of iOS 9.3.3.)


There's a surprising variety of just "English" accent voices as 
well. "South Africa", for example, has its own "voice". My current 
settings list "Samantha" (enhanced) American accent as what I used last 
though it's been a while since I've used it. I think I've probably also 
tried out a little the British "Siri" female voice as well.


-TS

On 2/10/2017 3:43 AM, David Haslam wrote:

After all these years of owning an iPad Mini & iPhone 5, I just found out
that iOS devices do have TTS capability.

So I just updated this section of our wiki page.

https://crosswire.org/wiki/Choosing_a_SWORD_program#Other

Quite a number of languages are supported when you select Voice.
I've just installed the English (UK) voice called Daniel (Enhanced) 188 MB,
but the default voice was quite acceptable.

Of course, being quite general, you can't make it exclude the verse numbers
in the selected passage.

Best regards,

David




--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/PocketSword-can-speak-tp4656672.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



--
- Timothy


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Are the code libraries which come with the SWORD library such as clucene, zlib, etc. the same as from the source or are they modified?

[TS]

 since Linux should be using the same 
64 bit standard as what Apple uses so the 64bit warnings should affect them as 
well. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Does Eloquent use only the core library of SWORD or more than that? e.g. the clucene library, zlib, etc.

[TS]

Does Eloquent use only the core library of SWORD or more than that? e.g. the 
clucene library, zlib, etc. 

I took a look at its source code, but the Sword code is pre-bundled into what 
Apple defines as a framework for Xcode and this seems to hide away everything 
except for header files. 

I'm interested in finding this info out because of the recent 64 bit issues 
I've written earlier about and because, for example, it seems that nether the 
clucene code nor zlib code is being maintained anymore. Since I've been trying 
to work on the PocketSword code, I'm curious as to how its desktop counterpart 
handles tasks. Does it use the same libraries of code that comes with the SWORD 
code or if not, which ones are used and which ones are not?

 zlib btw is somewhat odd on iOS. It is not plug and play. A file needs to be 
modified in zlib folder in order for it to work. However, when troubleshooting 
the issues on the internet, a lot of people with similar problems got replies 
back that zlib already comes in one of Apple's libraries. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

Hi Manfred,
I took a look at these wrapper files in the bindings/objc for Revision 
3441 of the SWORD framework. Using FileMerge I compared it to what seems to be 
the wrapper files in PocketSword. Upon at least a simple comparison, there 
seems to be some similarities, but also some huge differences as well. 
FileMerge highlighted quite a lot of things. I remember that at least one 
header file has the same name, but other than that the header seems to have 
completely different code. It was a surprise.

-TS

> On Oct 14, 2016, at 4:15 AM, Manfred Bergmann <manfred.bergm...@me.com> wrote:
> 
> I’m also having tons of warnings when compiling SWORD in Xcode for 64 bit.
> The precision warnings can be ignored IMO. But due to the sheer number of 
> warnings it’s very hard to detect warnings that shouldn’t be ignored.
> 
> Btw: there is a Objective-C wrapper for the SWORD library under bindings/objc 
> which I maintain and use in Eloquent.
> AFAIK some form of the wrapper in used in PS.
> It would be great if efforts could be shared in using only one codebase.
> 
> 
> 
> Manfred
> 
> 
>> Am 13.10.2016 um 22:30 schrieb TS <outofthec...@icloud.com 
>> <mailto:outofthec...@icloud.com>>:
>> 
>>  So, Xcode gives me hundreds of warnings when I try to build for 64 bit 
>> mode. I've also tried searching the mailing list so I see that some people 
>> earlier in the year may be have seen the same warnings (for PocketSword), so 
>> I think I better understand why I've seen that some of the libraries were 
>> updated(I don't know if all were updated or ?). However, I'm still getting 
>> errors and some of it is in the Sword framework. My impression so far of 
>> what's going on is that Xcode is telling me is that there are datatypes 
>> which are not being converted properly. I think this is happening due to 
>> things like "int" and "long" not occupying the same amount of space or 
>> something like they use to do in 32 bit and so need a casting in order to be 
>> converted properly?
>>  An example is listkey.h at line 147 in which "index" is a "long", but 
>> then setToElement is for an "int".
>>  Another is swbuf.h at line 448 "...const { unsigned int psize = 
>> strlen(postfix); ..." where Xcode warns that there's a loss of precision. 
>> That an unsigned long is converting to an unsigned int. I think that 
>> unsigned long occupies 64 bits when run in 64 bit mode, but the int stays in 
>> 32 bits when run in 64 bit mode.
>> I have compared the Sword framework that it's using against the last 
>> stable one and there's doesn't seem to be changes to address the issues I'm 
>> seeing.
>> Any suggestions on how to proceed?
>> 
>> -TS
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] #include in xzcomprs.cpp - is this a bug or ?

[TS]

In xzcomprs.cpp, at line 30, there’s the code:

#include 

Xcode was not happy about this since there is no header named this. It seems 
that in the previous version of PocketSword, the fix was just to set Xcode as 
to not include this file when compiling so that’s what I’m doing too. Since the 
SWORD framework does not include lzma.h as a file, this seems like a bug to me, 
but perhaps there's a reason for it?

I couldn’t find any reference regarding this matter in specific in the wiki or 
mailing list.


-TS___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

Hi,

Ok, so I was able to download Revision 3441 which I think is the most recent 
version of SWORD? (at least at the time.)

I’ve been working on getting it to work with the PocketSword code. There’s a 
bit of code and changes which needed to be made in order for it to work. I 
thought I could just replace the old code, but it doesn’t work like that. Are 
these changes documented anywhere? There’s only some listed in the SWORD-HOWTO 
named file that’s in the /objc/doc folder of the Bindings folder. I’ve been 
troubleshooting through in order to get things working. Also, I eventually 
wound up running a comparison of the entire Sword folder to what currently 
exists in order to find the differences in the code parts.

Has there been any more updates on the code to make it more 64-bit ? 
It’s a lot better, but there’s still a lot of warnings regarding the matter 
that Xcode gives me. I’m considering the CLucene warnings as part of it all as 
well though I’m not sure if I should or not?

There also seems to be a couple of bugs or so, which I’ll put in the tracker.

Also, I’m not sure if it matters or not, but just fyi, Xcode 7.3.1 uses C99 for 
the C language dialect.

-TS  

> On Oct 25, 2016, at 1:32 AM, Peter von Kaehne <ref...@gmx.net> wrote:
> 
> Check out our wiki, it has repos etc listed. 
> 
> Sent from my phone. Apologies for brevity and typos.On 25 Oct 2016 9:09 am, 
> TS <outofthec...@icloud.com> wrote:
>> 
>> Thank you! For the codebase that you updated, is there somewhere that I can 
>> download it to see the changes?
>> 
>> Xcode is giving me warnings, not errors, so it is technically compiling ok 
>> in that regard. (However, that does not necessarily mean that it’s ok to 
>> compile things that way.)
>> 
>> Manfred and Jaak both wrote earlier in this thread regarding how it runs on 
>> Mac and Linux. There’s issues in both cases.
>> 
>> The last official release of PocketSword was not compiled for 64-bit as far 
>> as I can tell from the download on the website for it. The project’s setting 
>> is set for 32-bit only, and not for 64-bit, though I could be mistaken.
>> 
>> Your welcome reg. the bug report.
>> 
>> -TS
>> 
>>> On Oct 23, 2016, at 1:44 AM, Troy A. Griffitts <scr...@crosswire.org> wrote:
>>> 
>> Dear TS,
>> 
>> Thank you for the spreadsheet.  I've had a review of the implicit cast 
>> warning and determined where the casts were safe and added explicit casts.  
>> This should remove most of these warnings for you.  Have you actually had a 
>> problem compiling SWORD for 64bit or were just concerned about warnings?  
>> Manfred and Nic should be able to answer better, but I'm quite sure we've 
>> been running 64bit on OSX for quite some time; not sure about iOS.
>> 
>> Thanks also for the report on the missing [] in the delete in swld.
>> 
>> You should have better results with svn HEAD.  Please keep us posted.
>> 
>> Troy
>> 
>>  
>> On 10/19/2016 12:58 PM, TS wrote:
>> 
>> Hi Peter, thank you for your help in this. I made the following for you and 
>> anyone else interested. I hope it’ll help you better identify and understand 
>> the warnings and/or type of warnings that we are seeing. I’m not really that 
>> familiar with how clang and llvm nor autotools works so I don’t know what 
>> changes to suggest so this is the next best thing that I thought of. 
>> (Perhaps it is something I should investigate…?)
>> 
>>  In order to create the numeric breakdown that I posted earlier, I 
>> copied and pasted the warnings Xcode gave me into a spreadsheet and sorted 
>> the data. Here is a copy of the final spreadsheet that was done:
>> 
>> https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods
>> 
>>  On the left columns, I’ve used formulas to label which are warnings 
>> occurring in a Sword file or CLucene file. Whatever is not one of those is 
>> something else, but those are a minor amount in comparison and I think are 
>> PocketSword files unrelated to the Sword framework files. 
>> There’s also 3 warnings which are not 64-bit related which I’ve marked in 
>> yellow and that I already know about.
>> 
>> On the right side of the sheet, I separated out the file locations and their 
>> matching warnings into separate columns.
>> 
>> So, overall, this should give you an organized list of the warnings that 
>> Xcode gives providing the file name and the warning. Next to the file names 
>> are numbers. The first number is the row number in which the error occurs 
>> and then the second number is the number of spaces from the left that 

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

Thank you! For the codebase that you updated, is there somewhere that I can 
download it to see the changes?

Xcode is giving me warnings, not errors, so it is technically compiling ok in 
that regard. (However, that does not necessarily mean that it’s ok to compile 
things that way.)

Manfred and Jaak both wrote earlier in this thread regarding how it runs on Mac 
and Linux. There’s issues in both cases.

The last official release of PocketSword was not compiled for 64-bit as far as 
I can tell from the download on the website for it. The project’s setting is 
set for 32-bit only, and not for 64-bit, though I could be mistaken.

Your welcome reg. the bug report.

-TS

> On Oct 23, 2016, at 1:44 AM, Troy A. Griffitts <scr...@crosswire.org> wrote:
> 
> Dear TS,
> Thank you for the spreadsheet.  I've had a review of the implicit cast 
> warning and determined where the casts were safe and added explicit casts.  
> This should remove most of these warnings for you.  Have you actually had a 
> problem compiling SWORD for 64bit or were just concerned about warnings?  
> Manfred and Nic should be able to answer better, but I'm quite sure we've 
> been running 64bit on OSX for quite some time; not sure about iOS.
> 
> Thanks also for the report on the missing [] in the delete in swld.
> 
> You should have better results with svn HEAD.  Please keep us posted.
> 
> Troy
> 
>  
> On 10/19/2016 12:58 PM, TS wrote:
>> Hi Peter, thank you for your help in this. I made the following for you and 
>> anyone else interested. I hope it’ll help you better identify and understand 
>> the warnings and/or type of warnings that we are seeing. I’m not really that 
>> familiar with how clang and llvm nor autotools works so I don’t know what 
>> changes to suggest so this is the next best thing that I thought of. 
>> (Perhaps it is something I should investigate…?)
>> 
>>  In order to create the numeric breakdown that I posted earlier, I 
>> copied and pasted the warnings Xcode gave me into a spreadsheet and sorted 
>> the data. Here is a copy of the final spreadsheet that was done:
>> 
>> https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods 
>> <https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods>
>> 
>>  On the left columns, I’ve used formulas to label which are warnings 
>> occurring in a Sword file or CLucene file. Whatever is not one of those is 
>> something else, but those are a minor amount in comparison and I think are 
>> PocketSword files unrelated to the Sword framework files. 
>> There’s also 3 warnings which are not 64-bit related which I’ve marked in 
>> yellow and that I already know about.
>> 
>> On the right side of the sheet, I separated out the file locations and their 
>> matching warnings into separate columns.
>> 
>> So, overall, this should give you an organized list of the warnings that 
>> Xcode gives providing the file name and the warning. Next to the file names 
>> are numbers. The first number is the row number in which the error occurs 
>> and then the second number is the number of spaces from the left that the 
>> warning is at. (Tabs/indents seem to count as one space)
>> 
>> I kept it as an OpenOffice doc in order to preserve the formulas I used to 
>> sort the errors. It should help you to organize and sort the data if you so 
>> desire. If you can’t open it though, just let me know and I can save it in a 
>> different format and etc.
>> 
>> Thank you,
>> TS
>> 
>>> On Oct 19, 2016, at 2:44 AM, Peter Von Kaehne <ref...@gmx.net 
>>> <mailto:ref...@gmx.net>> wrote:
>>> 
>>>> Gesendet: Mittwoch, 19. Oktober 2016 um 09:24 Uhr
>>>> Von: "Manfred Bergmann" <manfred.bergm...@me.com 
>>>> <mailto:manfred.bergm...@me.com>>b. Is it possible that 
>>>> 
>>>> Per default Xcode uses the C compiler of LLVM.
>>> 
>>> Ok. 
>>> 
>>> I have tried compiling with clang/llvm on Linux just now, but likely made a 
>>> few/lot mistakes
>>> 
>>> CC=clang ./configure 
>>> make
>>> 
>>> produced a few (less than 10) warnings re string/char  conversions at one 
>>> point, in one function only but worked as such. Not tried the result.
>>> 
>>> CC=clang++ ./configure
>>> make 
>>> 
>>> produced the same warnings but then failed at the linking stage. 
>>> 
>>> But the config.log had still ample references to gcc so I am not sure if 
>>> this was really the right approach. Can you suggest how to change the 
>

Re: [sword-devel] Older iOS devices and future PocketSword releases?

[TS]

Regarding the API compatibility, I’m still not sure if I fully understand it. 
My current understanding is that each iPhone/iPad will interpret the app’s code 
based on the iOS it’s running. So, if a lot of code is completely deprecated 
and replaced in a new SDK (or API) release, you still need to keep the old code 
so that the iPhone/iPad’s still running on the older iOS’s will still work 
correctly. I think that when things like that happen the code should be 
commented or explained or etc. so that the code is organized and not confusing 
or hard to follow or etc. 
 On a related note though, updated API’s seem to also allow for changes to 
functions (methods) behind the scenes. I think that the current iTunes version 
of PocketSword can’t download certain search indices due to an issue like this. 
The methods for downloading data from the internet were completely reworked and 
somewhere along the line, it was no longer allowed to block the main thread 
which I think may be at least part of the reason why it stopped working.

Here’s some results of some experiments I did running PocketSword 1.4.7 on an 
older version of Xcode:
With Xcode 6.2 using iPhone 5s as the model to simulate on and using a base SDK 
of iOS 8.2 for every test.
Simulating on an iPhone running iOS 7.1  YES - search index downloads
Simulating on an iPhone running iOS 8.1  NO - will not download search index
Simulating on an iPhone running iOS 8.2  NO - will not download search index

Also, on a related note, I saw some articles online which say that Apple allows 
developers to offer older versions of their app through the store so that 
devices running an older iOS can download those versions which are still 
compatible. Here’s a stack overflow link which has some pictures:
http://stackoverflow.com/questions/19147885/app-store-managing-availability-of-your-apps-previous-versions
 
<http://stackoverflow.com/questions/19147885/app-store-managing-availability-of-your-apps-previous-versions>

Hope this helps,
TS



> On Oct 22, 2016, at 3:50 AM, Manfred Bergmann <manfred.bergm...@me.com> wrote:
> 
> 32 + 64 bit is not a problem.
> Xcode will usually build multiple architectures and combine them in one app.
> 
> The issue is API compatibility.
> When building with the latest Xcode the oldest iOS target version is iOS 8.
> That means any new build of PocketSword will probably not be able to target 
> anything below that.
> 
> 
> Manfred
> 
>> Am 22.10.2016 um 12:29 schrieb David Haslam <dfh...@googlemail.com>:
>> 
>> Assuming that the programmers eventually succeed in getting the 64bit version
>> of PocketSword compiled without errors, may I remind developers that there
>> are still many users who, like me, have older iOS devices that are only
>> 32bit. 
>> 
>> We don't want to abandon PocketSword users that have older machines. It's
>> impossible to install a 64bit app into a 32bit device.
>> 
>> Some app developers therefore have two editions of each app, one for 64bit
>> devices and one for 32bit devices. For example, the iOS app called VPN
>> Unlimited from KeepSolid.
>> 
>> Not being an iOS app developer, I don't know if there is an alternative way
>> to resolve this, other than having two separate apps. 
>> 
>> (I've seen Windows apps that detect whether the processor is 32bit or 64bit,
>> and which proceed with the installation accordingly. There are further
>> complications in 64bit PCs, as the updater ideally needs to detect any
>> previous 32bit version of the program, and offer to first delete that before
>> installing the 64bit version.)
>> 
>> Please remember this as the project proceeds. Thanks.
>> 
>> 
>> Best regards,
>> 
>> David
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://sword-dev.350566.n4.nabble.com/Older-iOS-devices-and-future-PocketSword-releases-tp4656505.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>> 
>> ___
>> sword-devel mailing list: sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Older iOS devices and future PocketSword releases?

[TS]

Yes, Manfred is correct. To go into more detail, the settings I’ve been using 
are the defaults for Xcode 7.3.1 which are armv7 and arm64. Armv7 should work 
for all iPhone and iPads running in 32 bit mode except for the very early 
models. I looked through Apple’s documentation on it to see what each model ran 
on.
Here’s also a website with a chart I found:
http://iossupportmatrix.com/

On Xcode, you can manually set how far back an iOS version to support. I think 
Nic has already been doing that to support iOS 5.1.1. I’ve been using iOS 6 due 
in part to the last mailing list posting I did regarding how old the support 
should be. 

-TS


> On Oct 22, 2016, at 3:50 AM, Manfred Bergmann <manfred.bergm...@me.com> wrote:
> 
> 32 + 64 bit is not a problem.
> Xcode will usually build multiple architectures and combine them in one app.
> 
> The issue is API compatibility.
> When building with the latest Xcode the oldest iOS target version is iOS 8.
> That means any new build of PocketSword will probably not be able to target 
> anything below that.
> 
> 
> Manfred
> 
>> Am 22.10.2016 um 12:29 schrieb David Haslam <dfh...@googlemail.com>:
>> 
>> Assuming that the programmers eventually succeed in getting the 64bit version
>> of PocketSword compiled without errors, may I remind developers that there
>> are still many users who, like me, have older iOS devices that are only
>> 32bit. 
>> 
>> We don't want to abandon PocketSword users that have older machines. It's
>> impossible to install a 64bit app into a 32bit device.
>> 
>> Some app developers therefore have two editions of each app, one for 64bit
>> devices and one for 32bit devices. For example, the iOS app called VPN
>> Unlimited from KeepSolid.
>> 
>> Not being an iOS app developer, I don't know if there is an alternative way
>> to resolve this, other than having two separate apps. 
>> 
>> (I've seen Windows apps that detect whether the processor is 32bit or 64bit,
>> and which proceed with the installation accordingly. There are further
>> complications in 64bit PCs, as the updater ideally needs to detect any
>> previous 32bit version of the program, and offer to first delete that before
>> installing the 64bit version.)
>> 
>> Please remember this as the project proceeds. Thanks.
>> 
>> 
>> Best regards,
>> 
>> David
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://sword-dev.350566.n4.nabble.com/Older-iOS-devices-and-future-PocketSword-releases-tp4656505.html
>> Sent from the SWORD Dev mailing list archive at Nabble.com.
>> 
>> ___
>> sword-devel mailing list: sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[TS]

I posted about it on the SWORD api bug tracker. It’s 
http://crosswire.org/tracker/browse/API-190 
. It seems to have been fixed.

-TS___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

Hi Peter, thank you for your help in this. I made the following for you and 
anyone else interested. I hope it’ll help you better identify and understand 
the warnings and/or type of warnings that we are seeing. I’m not really that 
familiar with how clang and llvm nor autotools works so I don’t know what 
changes to suggest so this is the next best thing that I thought of. (Perhaps 
it is something I should investigate…?)

 In order to create the numeric breakdown that I posted earlier, I copied 
and pasted the warnings Xcode gave me into a spreadsheet and sorted the data. 
Here is a copy of the final spreadsheet that was done:

https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods 
<https://dl.dropboxusercontent.com/u/1472406/XCode%20Warnings.ods>

 On the left columns, I’ve used formulas to label which are warnings 
occurring in a Sword file or CLucene file. Whatever is not one of those is 
something else, but those are a minor amount in comparison and I think are 
PocketSword files unrelated to the Sword framework files. 
There’s also 3 warnings which are not 64-bit related which I’ve marked in 
yellow and that I already know about.

On the right side of the sheet, I separated out the file locations and their 
matching warnings into separate columns.

So, overall, this should give you an organized list of the warnings that Xcode 
gives providing the file name and the warning. Next to the file names are 
numbers. The first number is the row number in which the error occurs and then 
the second number is the number of spaces from the left that the warning is at. 
(Tabs/indents seem to count as one space)

I kept it as an OpenOffice doc in order to preserve the formulas I used to sort 
the errors. It should help you to organize and sort the data if you so desire. 
If you can’t open it though, just let me know and I can save it in a different 
format and etc.

Thank you,
TS

> On Oct 19, 2016, at 2:44 AM, Peter Von Kaehne <ref...@gmx.net> wrote:
> 
>> Gesendet: Mittwoch, 19. Oktober 2016 um 09:24 Uhr
>> Von: "Manfred Bergmann" <manfred.bergm...@me.com>b. Is it possible that 
>> 
>> Per default Xcode uses the C compiler of LLVM.
> 
> Ok. 
> 
> I have tried compiling with clang/llvm on Linux just now, but likely made a 
> few/lot mistakes
> 
> CC=clang ./configure 
> make
> 
> produced a few (less than 10) warnings re string/char  conversions at one 
> point, in one function only but worked as such. Not tried the result.
> 
> CC=clang++ ./configure
> make 
> 
> produced the same warnings but then failed at the linking stage. 
> 
> But the config.log had still ample references to gcc so I am not sure if this 
> was really the right approach. Can you suggest how to change the compiler 
> properly within the autotools setup? 
> 
> Peter
> 
> ___
> sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

Thank you all for your replies and suggestions.

  I could go in to more detail, but here’s a summary breakdown of the 
warnings and what they connect to. (There are 3 warnings included in all this 
which I am aware of which are not necessarily 64 bit related)

Summary:
- There are 96 warnings found in files inside of the CLucene (clucene/CLucene) 
folder
- There are 185 warnings which are in the externals/sword folders.
- There are 32 warnings which are in the externals/CocoaHTTPServer folder.
- There are 10 warnings which are in the Classes folder. These seem to be
  written especially for PocketSword and are not part of libraries or 
frameworks.

 From what I’m seeing so far, all the warnings are mostly repeating 
variations of the same thing which is that there is a datatype which in 64 bit 
runtime is a 64 bit quantity and the code is assigning it to an “int” value 
which is a 32 bit quantity. The data type “long” is a 64 bit quantity, for 
example, and so a warning is thrown every time it’s assigned to an “int” 
datatype which remains a 32 bit quantity when running in a 64 bit runtime. 
Here’s a link which shows Apple’s documentation regarding how their data types 
change based on the 32 or 64 runtime. 

https://developer.apple.com/library/content/documentation/General/Conceptual/CocoaTouch64BitGuide/Major64-BitChanges/Major64-BitChanges.html
 
<https://developer.apple.com/library/content/documentation/General/Conceptual/CocoaTouch64BitGuide/Major64-BitChanges/Major64-BitChanges.html>

If I’m mistaken though, please somebody let me know.

 From all the online research I’ve been doing trying to figure the problems 
out, it’s sorta leading me to the question "Has the SWORD framework been 
updated to be 64 bit compatible?” I’ve searched the Sword project wiki and 
searched what I can of the mailing list, but I can’t find any definitive answer.

 Also, in case it’s not known, Windows in comparison to Mac/Unix/Linux uses 
a different 64 bit convention. Mac (including iPhone) uses LP64. So, long or 
long int, for example, is a 64-bit quantity, but for Windows it remains a 
32-bit quantity even when run in the 64-bit runtime. So, is it possible that 
the SWORD framework does not have the same warnings that I get when compiled on 
a computer running the Windows OS? 

 I get the impression that these warnings can be ignored and the program 
work as long as the values that the long, unsigned long, or etc. hold never 
exceed a 32-bit size? and errors only occur if they are exceeded?

 I’m concerned about these 64-bit warnings because it’s my understanding 
that Apple requires apps to be 64-bit compatible and they vet each app for 
entry into the store. So, I don’t know how these warnings would be treated by 
them. I can see why Xcode or the compiler is treating them as warnings since 
they are apparantly correct in the 32-bit runtime. However, it seems that there 
is a “proper” way to convert the data types from one to another which works in 
both 32 and 64-bit runtimes? and since the code does not do that, Xcode assumes 
that it is either pre-64-bit code or that it is an erroneous typed line of code 
and hence gives a warning?

 Sorry, if I’m way off on any of this. If you’ve read all this, thank you, 
I know it’s a lot.

-TS


> On Oct 14, 2016, at 4:58 AM, Peter Von Kaehne <ref...@gmx.net> wrote:
> 
> https://developer.apple.com/library/content/documentation/Darwin/Conceptual/64bitPorting/building/building.html
>  
> suggests that some flags are less useful than others in terms of warnings 
> produced - some flags produce a plethora of spurious and irrelevant warnings
>  
> Is that maybe part of your problem?
>  
> Peter
>  
> Gesendet: Freitag, 14. Oktober 2016 um 12:15 Uhr
> Von: "Manfred Bergmann" <manfred.bergm...@me.com>
> An: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
> Betreff: Re: [sword-devel] How do you make the Sword framework work in 64bit 
> mode? (My compiler is giving me hundreds of warnings.)
> I’m also having tons of warnings when compiling SWORD in Xcode for 64 bit.
> The precision warnings can be ignored IMO. But due to the sheer number of 
> warnings it’s very hard to detect warnings that shouldn’t be ignored.
>  
> Btw: there is a Objective-C wrapper for the SWORD library under bindings/objc 
> which I maintain and use in Eloquent.
> AFAIK some form of the wrapper in used in PS.
> It would be great if efforts could be shared in using only one codebase.
>  
>  
>  
> Manfred
>  
>  
> Am 13.10.2016 um 22:30 schrieb TS <outofthec...@icloud.com 
> <mailto:outofthec...@icloud.com>>:
>  
>  So, Xcode gives me hundreds of warnings when I try to build for 64 bit 
> mode. I've also tried searching the mailing list so I see that some people 
> earlier in the year may be h

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[TS]

I see. The code I just uploaded has the brackets, but I’ve made a note to undo 
it I guess and figure out how to get it fixed in the Sword repo. 

Thanks,
TS

> On Oct 13, 2016, at 11:56 AM, Manfred Bergmann <manfred.bergm...@me.com> 
> wrote:
> 
> Hi.
> 
> 
>> Am 13.10.2016 um 20:28 schrieb TS <outofthec...@icloud.com 
>> <mailto:outofthec...@icloud.com>>:
>> 
>>  Thank you all for your replies and confirmation. I will use the delete 
>> with the square brackets. 
> 
> I would suggest to stick to the upstream code as much as possible. That 
> means, have someone fix this in the main SWORD repo and pull a copy of it for 
> PS.
> Otherwise it’s hard to reason what exactly is used in PS.
> 
> 
> Manfred
> 
> 
>> 
>>  I also had already looked at the Sword++ code and saw that it had the 
>> brackets which suggested to me that it was correct that something should be 
>> there. 
>>  I had some confusion because in Apple's ObjC framework, they also have 
>> a "new" function and Xcode was directing me to it when I was asking it to 
>> show me where "new" came.(The "new" use to created the variable which needed 
>> delete[]). As a result, I was uncertain as to how Xcode was implementing the 
>> code. I think though that it may be an error for Xcode to be directing me to 
>> the Cocoa definition of "new" since the file has the "cpp" file extension 
>> and so Xcode should know to expect c++ code. Also, "new" isn't being applied 
>> here in the code as a proper objective-c method call (I don't think?), so 
>> I'm thinking that it's being compiled as the "new" from the c++ library.
>> 
>> Thanks again,
>> -TS
>> 
>> On Oct 12, 2016, at 05:16 AM, DM Smith <dmsm...@crosswire.org 
>> <mailto:dmsm...@crosswire.org>> wrote:
>> 
>>> 
>>>> On Oct 12, 2016, at 3:22 AM, Jaak Ristioja <j...@ristioja.ee 
>>>> <mailto:j...@ristioja.ee>> wrote:
>>>> On 12.10.2016 10:02, Manfred Bergmann wrote:
>>>>> 
>>>>>> Am 12.10.2016 um 08:57 schrieb Jaak Ristioja <j...@ristioja.ee 
>>>>>> <mailto:j...@ristioja.ee>>:
>>>>>> 
>>>>>> On 12.10.2016 09:37, Manfred Bergmann wrote:
>>>>>>>> On 12.10.2016 01:08, TS wrote:
>>>>>>>>> Xcode was warning me that in PocketSword's Sword framework, swld.cpp 
>>>>>>>>> at
>>>>>>>>> line 111 with
>>>>>>>>> 
>>>>>>>>> "delete buf;"
>>>>>>>>> may be wrong and it should perhaps be
>>>>>>>>> 
>>>>>>>>> "delete[] buf;"
>>>>>>>>> instead. Is this correct? I looked at the code and I think Xcode is
>>>>>>>>> correct in that the variable is an array and needs the brackets to
>>>>>>>>> delete properly.
>>>>>>>> 
>>>>>>>> Yes, Xcode has it correct. It should be `delete[] buf;`. This was also
>>>>>>>> fixed in Sword++ in March.
>>>>>>> 
>>>>>>> Despite the warning, would but not be deleted completely?
>>>>>> 
>>>>>> It is undefined behavior, as stated by §3.7.4.2.3 in C++11. However, the
>>>>>> C++ draft at https://github.com/cplusplus/draft 
>>>>>> <https://github.com/cplusplus/draft> doesn't have this
>>>>>> wording since e51a2152 [1] for some reason.
>>>>>> 
>>>>> 
>>>>> Yeah, don’t get me wrong. It should be corrected.
>>>>> But is it indeed a memory leak or does the runtime still collect and 
>>>>> destroy all array elements?
>>>>> Depends on the runtime probably.
>>>> 
>>>> It is undefined behavior (see http://stackoverflow.com/q/2397984/3919155 
>>>> <http://stackoverflow.com/q/2397984/3919155>
>>>> ). So as far as the C++ standard is concerned, this might yield
>>>> different behavior depending on the toolchain, the runtime, the
>>>> environment or the phase of the moon... There are also no defined bounds
>>>> to what may happen: it may leak, crash, hang, corrupt memory, whatever...
>>>> 
>>>> J
>>>> 
>>> 
>>> If I recall delete without the brackets will delete the object. 

Re: [sword-devel] How can I tell which version of the Sword framework is being used? (e.g. in PocketSword)

[TS]

 I’ve uploaded the code of where I’m at currently at:
https://bitbucket.org/blue22/ps-proj

  I’ve been trying and trying to get the Sourcetree/Mercurial/Bitbucket to 
let me create a branch off the main code, change it to what i have, upload it, 
and then submit a pull request…but it keeps rejecting my requests to upload the 
code into a new branch. I have been trying and trying to do it, but I don’t 
know what I’m doing wrong. :(   

  I’ve been trying to debug mostly in categories that Xcode displays its 
bug report in. I altered the the build settings file(s) so that I could narrow 
down the bugs and focus on a category so, for example, deprecations warnings 
are turned off for now since I’ve been focusing on 64 bit conversion warnings.

-TS


> On Oct 12, 2016, at 11:29 PM, Nic Carter <niccar...@mac.com> wrote:
> 
> PS was periodically updated from SVN, with minor tweaks.
> 
> https://bitbucket.org/niccarter/pocketsword/commits/2a000dccffb458bc9893f4e5f45e00fd9bb3e18e
>  
> <https://bitbucket.org/niccarter/pocketsword/commits/2a000dccffb458bc9893f4e5f45e00fd9bb3e18e>
> 
> Above commit seems to be the last sync. I have no idea what rev SWORD is at 
> now, nor what changes have been made to it since r3257.
> 
> Life has become messy again, so while I will strive to keep an eye on things, 
> I most likely won’t touch code until December? It would be most awesome if 
> any changes from the latest rev of PS on BitBucket were placed somewhere and 
> you created a Pull Request so I could quickly and easily look at any changes 
> and integrate them. Right now there are zero, so that means I have to 
> manually look at changes and play with them --> 
> https://bitbucket.org/niccarter/pocketsword/pull-requests/ 
> <https://bitbucket.org/niccarter/pocketsword/pull-requests/> 
> 
> 
> Thanks,
> Nic.
> 
>> On 12 Oct. 2016, at 9:13 am, TS <outofthec...@icloud.com 
>> <mailto:outofthec...@icloud.com>> wrote:
>> 
>> Hi,
>> 
>> How can I tell which version of the Sword framework is being used? ( e.g. in 
>> PocketSword.) I've done a search of the code and some comparison to two 
>> different versions of the framework, but nether version 1.7.5 nor 1.6.2 seem 
>> to match. Is there a place where it's stated?
>> 
>> -TS
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How can I tell which version of the Sword framework is being used? (e.g. in PocketSword)

[TS]

It's looking like I won't be able to upload the code today. It'll hopefully be 
during the weekend or else next week then instead. 

-TS

--Sent from phone--
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] How do you make the Sword framework work in 64bit mode? (My compiler is giving me hundreds of warnings.)

[TS]

     So, Xcode gives me hundreds of warnings when I try to build for 64 bit mode. I've also tried 
searching the mailing list so I see that some people earlier in the year may be have seen the same 
warnings (for PocketSword), so I think I better understand why I've seen that some of the libraries 
were updated(I don't know if all were updated or ?). However, I'm still getting errors and some of 
it is in the Sword framework. My impression so far of what's going on is that Xcode is telling me 
is that there are datatypes which are not being converted properly. I think this is happening due 
to things like "int" and "long" not occupying the same amount of space or 
something like they use to do in 32 bit and so need a casting in order to be converted properly?
     An example is listkey.h at line 147 in which "index" is a "long", but then 
setToElement is for an "int".
     Another is swbuf.h at line 448 "...const { unsigned int psize = 
strlen(postfix); ..." where Xcode warns that there's a loss of precision. That an 
unsigned long is converting to an unsigned int. I think that unsigned long occupies 64 
bits when run in 64 bit mode, but the int stays in 32 bits when run in 64 bit mode.
    I have compared the Sword framework that it's using against the last stable 
one and there's doesn't seem to be changes to address the issues I'm seeing.
    Any suggestions on how to proceed?

-TS___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How can I tell which version of the Sword framework is being used? (e.g. in PocketSword)

[TS]

Thank you all for your answers. The framework in PS did not seem to be the most 
recent version, but I couldn’t tell how old it was or if any special tweaks had 
been made to it either. 

Thanks for the life update Nic. I’ve also been thinking of uploading the work 
I’ve been doing on PockedSword to an online repo and it seems that your 
prompting also supports that idea. I’ll see what I can do. Hopefully I’ll have 
something uploaded by the weekend.

Thanks,
TS



> On Oct 12, 2016, at 11:29 PM, Nic Carter <niccar...@mac.com> wrote:
> 
> PS was periodically updated from SVN, with minor tweaks.
> 
> https://bitbucket.org/niccarter/pocketsword/commits/2a000dccffb458bc9893f4e5f45e00fd9bb3e18e
>  
> <https://bitbucket.org/niccarter/pocketsword/commits/2a000dccffb458bc9893f4e5f45e00fd9bb3e18e>
> 
> Above commit seems to be the last sync. I have no idea what rev SWORD is at 
> now, nor what changes have been made to it since r3257.
> 
> Life has become messy again, so while I will strive to keep an eye on things, 
> I most likely won’t touch code until December? It would be most awesome if 
> any changes from the latest rev of PS on BitBucket were placed somewhere and 
> you created a Pull Request so I could quickly and easily look at any changes 
> and integrate them. Right now there are zero, so that means I have to 
> manually look at changes and play with them --> 
> https://bitbucket.org/niccarter/pocketsword/pull-requests/ 
> <https://bitbucket.org/niccarter/pocketsword/pull-requests/> 
> 
> 
> Thanks,
> Nic.
> 
>> On 12 Oct. 2016, at 9:13 am, TS <outofthec...@icloud.com 
>> <mailto:outofthec...@icloud.com>> wrote:
>> 
>> Hi,
>> 
>> How can I tell which version of the Sword framework is being used? ( e.g. in 
>> PocketSword.) I've done a search of the code and some comparison to two 
>> different versions of the framework, but nether version 1.7.5 nor 1.6.2 seem 
>> to match. Is there a place where it's stated?
>> 
>> -TS
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org 
>> <mailto:sword-devel@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@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] swld.cpp at line 111 - is this a bug?

[TS]

     Thank you all for your replies and confirmation. I will use the delete 
with the square brackets.

     I also had already looked at the Sword++ code and saw that it had the 
brackets which suggested to me that it was correct that something should be 
there.
     I had some confusion because in Apple's ObjC framework, they also have a "new" function and Xcode was directing me to it when I was 
asking it to show me where "new" came.(The "new" use to created the variable which needed delete[]). As a result, I was uncertain 
as to how Xcode was implementing the code. I think though that it may be an error for Xcode to be directing me to the Cocoa definition of 
"new" since the file has the "cpp" file extension and so Xcode should know to expect c++ code. Also, "new" isn't being 
applied here in the code as a proper objective-c method call (I don't think?), so I'm thinking that it's being compiled as the "new" from 
the c++ library.

Thanks again,    
-TS

On Oct 12, 2016, at 05:16 AM, DM Smith <dmsm...@crosswire.org> wrote:


On Oct 12, 2016, at 3:22 AM, Jaak Ristioja <j...@ristioja.ee> wrote:
On 12.10.2016 10:02, Manfred Bergmann wrote:

Am 12.10.2016 um 08:57 schrieb Jaak Ristioja <j...@ristioja.ee>:

On 12.10.2016 09:37, Manfred Bergmann wrote:
On 12.10.2016 01:08, TS wrote:
Xcode was warning me that in PocketSword's Sword framework, swld.cpp at
line 111 with

"delete buf;"
may be wrong and it should perhaps be

"delete[] buf;"
instead. Is this correct? I looked at the code and I think Xcode is
correct in that the variable is an array and needs the brackets to
delete properly.

Yes, Xcode has it correct. It should be `delete[] buf;`. This was also
fixed in Sword++ in March.

Despite the warning, would but not be deleted completely?

It is undefined behavior, as stated by §3.7.4.2.3 in C++11. However, the
C++ draft at https://github.com/cplusplus/draft doesn't have this
wording since e51a2152 [1] for some reason.


Yeah, don’t get me wrong. It should be corrected.
But is it indeed a memory leak or does the runtime still collect and destroy 
all array elements?
Depends on the runtime probably.

It is undefined behavior (see http://stackoverflow.com/q/2397984/3919155
). So as far as the C++ standard is concerned, this might yield
different behavior depending on the toolchain, the runtime, the
environment or the phase of the moon... There are also no defined bounds
to what may happen: it may leak, crash, hang, corrupt memory, whatever...

J


If I recall delete without the brackets will delete the object. That is the 
array. When called with the brackets will call delete on the elements in the 
array. In some cases the semantic difference does not matter, such as an array 
of char or int. I didn’t look at the code to see if it mattered here.

DM
___
sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] How can I tell which version of the Sword framework is being used? (e.g. in PocketSword)

[TS]

Hi,

How can I tell which version of the Sword framework is being used? ( e.g. in 
PocketSword.) I've done a search of the code and some comparison to two 
different versions of the framework, but nether version 1.7.5 nor 1.6.2 seem to 
match. Is there a place where it's stated?

-TS
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] swld.cpp at line 111 - is this a bug?

[TS]

Hi,

Xcode was warning me that in PocketSword's Sword framework, swld.cpp at line 
111 with

"delete buf;"
may be wrong and it should perhaps be

"delete[] buf;"
instead. Is this correct? I looked at the code and I think Xcode is correct in 
that the variable is an array and needs the brackets to delete properly.

-TS
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Announcing Sword++

[TS]

Hey everyone, maybe it would be a good idea to take a step back and 
cool off a bit? The messages are getting angry and somewhat personal. 
I'd like to think that no one here is trying to be bad or do anything 
wrong.
I think that people disagree with Jaak's decisions and think it's 
wrong and are therefore upset over it, but I get the impression that 
Jaak is and was also upset and frustrated back in May or else he would 
not have created the fork to begin with. Perhaps instead of arguing over 
Jaak's decisions we should be asking what can be done to address the 
problems that lead to the creation of the fork in the first place? It 
sounds like code submissions take too long to reach the trunk for 
example? How long does it take? Days, weeks, ...? Does there need to be 
more people with the ability to review and approve code submissions? 
etc. Perhaps improvements can be made for better communication? and 
feedback?
 Instead of arguing over Jaak's code, why don't we focus on asking 
"Hey, how can we take the good parts that he did and merge it back into 
the Sword code base?" I think it would help with the preserving and 
unity of the community.


I apologize if I'm speaking out of turn or ignorance. I'm not wishing to 
hurt anyone.

TS

On 9/26/2016 10:23 AM, Jaak Ristioja wrote:

On 26.09.2016 19:43, Peter von Kaehne wrote:

Given that there is, just as Matej points out, likely only "market" space for 
one library , I think success of your fork will mean exactly this - regression and 
breakage for those parts you are not interested in. You have made this very clear.

I also disagree with your market space theory regarding Sword/Sword++.
And how on earth did you reach to such conclusions about regressions and
breakage!? - I never said I will not support things I include in
Sword++. I only said that bindings and some other stuff will not be
included for the time being. Quite the contrary. And I'll keep pulling
fixes from Sword as well.


But, I guess, you are not in a mood to listen to this.

o_O You think? :D


Regards,
J

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



--
- Timothy   


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] What is the lowest version of iOS to be currently supported in PocketSword?

[TS]

I've been going through the code and making fixes, and in the process 
XCode has warned me that libcurl is for version iOS 6 and higher and 
also I've discovered that MBProgressHUD was also written for iOS 6 and 
higher. It seems that the external frameworks were updated from the 
previous release of PocketSword. So, is the lowest version supported iOS 
6 now? or is it still 5.1.1 and I can ignore the warnings? If 5.1.1 
should still be supported, do all of the newer frameworks still work 
with this version of the iOS or does compatibility need to be tested 
between iOS ver. 5.1.1 and the newer frameworks (and workarounds be 
implemented if need be)?


- Timothy

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[TS]

Hi,

Congratulations on your second child  :)

Thank you also for writing about the submittal and backwards compatibility of 
PocketSword. So much in iOS alone keeps changing…ARC, 64bit, and etc., I wonder 
how people keep up? but yes, at least it requires to constantly keep the apps 
up-to-date. :)

-Tim


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[TS]

Hi,
Thanks for the advice. To follow it, I’ve gone to the tracker page for 
PocketSword and added another comment with a link to the repo with the version 
that I had patched.

-Tim
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Apple Plans To Boot Orphaned Apps From its App Store

[TS]

Thank you for your and everyone else’s replies. I was not expecting it. It was 
encouraging. :) 
I’m not a professional at computer programming, so there are some things that I 
don’t know about, but I’m trying to learn. I’m not a stranger though to 
computers by any means. 

Thank you also for the information and details. It helps fill in some blanks 
and answer some question(s) that I had. For example, I had not realized that 
the search indexes were not self generated due to hardware limitations. 

I have used many of the modules from the Xiphos project, but I do not believe 
that I have used the actual program itself. I didn’t know that it could create 
search indexes. I may run a virtual instance of Linux just to try out Xiphos. 

I do have twitter and that’s one of the ways that I contacted Nic. I don’t 
tweet myself though really.

Before I forget, here is the link to my repo with the version of PocketSword 
that I patched and currently use:

https://bitbucket.org/blue22/codefornic

I only changed one file I think and tried to preserve what Nic had already 
written. I think offhand I may have made some other changes here and there 
too…I think I changed the http links to be https for example because of needing 
to conform to the newer security rules.

-Tim



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page