I am using iPad2

This is a really frustrating bug that we are currently looking into to try to solve!
However, we have discovered that the OT isn't being deleted, but simply refusing to load. So you don't need to delete the ESV and re-download it, instead you can quit the app and force quit it and launch it again and the whole of the ESV should be there again!

More details about forcing an app to close is available at http://support.apple.com/kb/HT5137?viewlocale=en_US&locale=en_US

And we're hoping to have a new version of PocketSword out as soon as this issue is solved

ipad

Hi Lee,

Unfortunately we are unable to provide such a feature for any iOS apps. You may only use fonts that come built-in to either the OS or to the app. Right now we have included one extra extra font, code2000, and the rest of the fonts available are available in iOS.

The example you provided is a feature available in a Mac app, not an iOS app. And the iOS version of their app doesn't allow installing of fonts.

Sorry about that!

yup. sigh

/me washes his hands of it and reassigns the bug.

iOS 6.1.2 on iPhone 4S. (Using 1.4.3, but will only allow me to select as high as 1.4.2)

Ahh, interesting suggestion!
It would be trivial for me to hard-code this so that you could switch on "auto night mode" & then it would be in night mode from, say, 8pm until 6:30am? But ideally you'd want this to be connected with another setting so each person could set their own times...

Let me think more about this
Thanks!

Sometimes I have bible studies till 9 or 10pm but sometimes in bed by then so I don't know. It just occurred to me that there is an ambient light sensor - perhaps that could be an option along with a time selection option. And/or perhaps a simple sun/moon toggling icon as a manual override.

I implemented an auto-night-mode feature in And Bible using the light sensor. If it is dark And Bible switches to Night mode automatically, if user has selected Settings/Auto night mode. Experiment to see what light sensor values you get in different environments and then pick a value, below which you switch to night mode.

I like this because sometimes I wake up at night and want to read the bible in bed but am almost blinded by the normal black-on-white screen (try it). This feature saved my eyes.

iOS 6.1.2 on iPhone 4S. (Using 1.4.3, but will only allow me to select as high as 1.4.2)

It sounds like your usage is similar to mine! The dictionary was added first, hence it's on the main page. However, I need to make it so that you can move the buttons around.
Also, thanks for letting me know about this tracker not knowing about v1.4.3 – I've fixed that now

Thanks for considering doing so!

iOS 6.1.2 on iPhone 4S.

Hi Marco, which devotional are you reading when you see this?
Those devotionals that are simply Bible readings (such as BibleCompanion, OneYearRead or MCheyne) will make the Bible reading open in the Bible tab. For all other devotionals it will appear in the small window at the bottom. I have picked the devotionals that seem most appropriate for the verse to appear in the Bible tab, but I am open to suggestions of others to add to this list!

Actually, I rolled my own using "For the Love of God" by D. A. Carson for my own personal use. Carson's work is a slight modification of MCheyne along with his own excellent commentary. Each day's commentary is a several paragraph commentary so maximum screen real estate is desirable.

Since Carson currently offers it freely online on his site (thegospelcoalition.org), I've contacted him requesting permission to redistribute it (hopefully via crosswire) and am awaiting a response.

Contact me offline if you're interested in details about this devotional.

Seems sorted with http://sidetweet.github.com/pocketsword-verses/
A Tour mode is not on the horizon, the URL stuff is a hidden feature, but implemented with the above website!
Highlighting is something that will be fixed, but that feature request is a duplicate of other bug reports

Thanks heaps!

iPhone 3S
IOS 4.1
Module: HunUj - The New Translation Bible for Hungarian Bible Society

Hi Janos,

It appears you are using an older version of the HunUj module.
Please try downloading the latest version from the CrossWire 3 (av11n) repository, which is available under the More tab & the Downloads.
I just downloaded the latest version of the module (which has its cross references fixed up) and 1 Cor 9 then looks different, as the links will then be replaced with an 'x' character, which you tap on to bring up the cross reference.

This is a module bug, which has been fixed, & so simply requires updating the module.
Marking as "cannot reproduce" as I cannot reproduce this with the latest version of the module.

Have you checked in any other of the Bible apps? Both BibleDesktop and AndBible work very differently to PocketSword (and use the same code), so I would want to know if it appears correctly in Xiphos, BibleTime or any of the other apps. I think this is a bug in the API rather than PocketSword, but please check for me!

Testing this in Xiphos, the behaviour is the same as in PocketSword. Evidence points to this being a badly formed module &/or a bug in the API. As there has been no further comments since my last comments where I asked for more information, I am going to close this bug. I don't believe it's a bug in PocketSword itself and unless there is further evidence to the contrary, I am leaving it at that and leaving it up to the reporter to report this bug to the API guys or the module guys.

iPad and iPhone

We are exploring other options for how to display the Strong's Numbers in the KJV, however we probably won't go with underlining at this point. Thanks for your suggestion and I'm glad you find the app such a blessing!

iOS 5

This won't be changed, as this is the intended behaviour. PocketSword won't work as a proper web browser, but will pull up certain web pages when required to provide additional information to what is embedded within a module. I hope you are able to find another app that will meet your needs.

iOS 5.0.1

Sorry topic i miss. That correct "Search result cannot find fully in Thai Bible"

This is because of the same issue as PS-59 is reporting about.
Marking as a duplicate.

can you give a verse number for where this occurs in the module you sent me?

have not heard back when I asked for further information, hence closing this "bug" due to incomplete information.

Feel free to file a new bug with more information if this is still relevant.

Is this a request for a preference to set a user-desired colour for the verse number? Also, what specifically are you asking for when wanting to assign a colour for a "section"?

you will see blue color for the section "Salutation" and gray color for the verse no.

Ahh, interesting. I'll think on it.

Hi again, could you please let me know of a module & verse position where this occurs so I can take a look into this?

The <hi type="xxx"> yyy yyy</hi> construct allows for xxx to indicate underline. The osishtmlhref.cpp filter does not handle that value (nor most of them). This report probably should be moved to API.

Here is an example:

<hi type="underline">AB</hi>c<hi type="underline">DEFG</hi>

I know Bible desktop for PC supports underline tag. See whether pocketsword will also support it in the future. Thanks.

Are there any other front-ends that support this? If it's only Bible Desktop, that is using JSword (Java) rather than our C++ API, which would infer that it is indeed an API issue, with osishtmlhref.cpp not supporting that.

See whether osishtmlhref.cpp will support it in the future. Thanks for your answer.

you'll need to give me a verse number so that I can find where this is happening in your module.

you will see the underline tag in Matthew 1:1. you can see this script in my file.

-----------
<hi type="underline">亞伯拉罕</hi>的後裔，
-----------

fixed.

please test in v1.4.2 of PocketSword, now available on the App Store.

Is this using a search index that you have created yourself or is it a search index that you downloaded from within PocketSword? And which module is it for?

AndBible uses JSword, which has much richer indexing and uses a Chinese analyzer for the text. SWORD uses StandardAnalyzer, which is appropriate only for some latinate languages. This is a request that SWORD have analysis based upon the language/script of the module.

A bit more info: most Lucene analyzers use whitespace to delineate words. This is not appropriate in some languages, such as Chinese. There are a variety of techniques to index Chinese, but to simplify: Suppose that there A, B, C were three Chinese characters and were given as ABC. This would index A, B, AB, C, and BC. In searching for AC, this would look for A, C and AC.

With the various whitespace analyzers, there would be no result. The text contained ABC and only ABC would find it.

The search index is created by PocketSword itself and it is a Chinese Module.

Thanks for the clarification, I will look into it.

Ok, I need some more clarification about this. You say that "The search index is created by PocketSword itself". However, PocketSword cannot create a search index – testing revealed that this would take a very long time and so I never added that code. So, how are you creating your search index? Is this in regard to the module that you sent me by email?

@DM thanks for that information, PS is still lacking in non-whitespace searches, such as Chinese.

It is my misunderstanding. The search index is created by "The sword Project" and I placed it into the module.

can you please give an example of a module and verse where this occurs so I can take a look at what it is doing? Thanks.

Here is an example:

---------------------
<chapter sID="Matt.1" osisID="Matt.1"/>
<div type="section">
<title type="section" subType="x-preverse">ABC</title>
<p>
<verse sID="Matt.1.1" osisID="Matt.1.1"/>
ABCDEFGHIJK
<verse eID="Matt.1.1"/>
<verse sID="Matt.1.2" osisID="Matt.1.2"/>
LMNOPQ
<verse eID="Matt.1.2"/>

---------------------

and the outcome is:

---------------------
ABC
1
ABCDEFGHIJK 2 LMNOPQ
---------------------

when using osis2mod.pl, the verses which are near the section will be fallen to next line.

ok, I don't think this is a PocketSword bug? Perhaps it is an API bug? What happens if you don't have the <p> in there? does it appear correctly? Does this appear as you wish in Xiphos or Eloquent or any other SWORD front-end?

But have you found this bug in any existing modules that you can download inside PocketSword? If not, I'm going to say that it's an API bug or something like that. I'm not an OSIS expert so I'm not sure if your OSIS is properly formed or anything like that...

I found it happened in Pocketsword and Eloquent but it worked correctly in The sword project, Xiphos, Bible desktop, AndBible.

Ok, at this point I'm going to need a SWORD module that contains the issue you have found. Shoot me an email.
Also, please take a look at http://crosswire.org/wiki/OSIS_Bibles#Marking_pre-verse_titles and especially Note 2. Are you sure you are wanting to be using x-preverse?

Final comment is that you may need to be asking others about your OSIS. I am in no way an OSIS expert and so I cannot tell if your OSIS is valid or if it will work with osis2mod properly and so I cannot know if PocketSword is behaving correctly or if it's an API issue?

Thanks!

Received my email? is the email address jira@crosswire.org?

ahh, no, sorry. Try niccarter [AT] mac [dot] com

received it?

This bug is probably in the API? But other modules with paragraphs work fine in PocketSword (such as the ESV), so perhaps you need to modify your OSIS for this to work? Unless you are certain that your OSIS is well formed, I am going to close this bug. But even if it is valid OSIS, our API does have certain issues that you can work around and still create valid OSIS. Perhaps you could email the sword-devel mailing list and ask there?

sorted. Also was visible in the LEB. see http://sword-dev.350566.n4.nabble.com/SWORD-handling-of-OSIS-paragraphs-td359793.html for more details of the mess!

Just another comment. I finally got around to testing this in Xiphos and it does not work as you said. I suggest that you go back and test your module properly in the different front-ends. I have tested it in the cutting-edge version of Xiphos (about to be released, I believe?), and it displays with the verse number on a different line to the verse text (for example, Luke ch1). Rather than ask each and every front-end to modify their code to get your module to work, I suggest you fix up your module so that it will work properly everywhere. That way you don't need to wait for them to update their applications?
Anyway, this fix will appear in the next version of PocketSword. :)

Thanks for your reply.
I found that Xiphos does not work indeed, but Bibledesktop works.

Please test this in v1.4.2 of PocketSword which was just released this week. Should work as intended now.

Hi there, I'll take a look into this, but would love to have a module and verse to look into – are you looking at a Greek New Testament module? Where is it from, and why does the NT have Job in it?

Here is an example:

-------------------
<div type="section">
<title type="section" subType="x-preverse">ABC</title>
<p>
<verse sID="Luke.1.1-Luke.1.4" osisID="Luke.1.1 Luke.1.2 Luke.1.3 Luke.1.4"/>
DEFGHIJK
<verse eID="Luke.1.1-Luke.1.4"/>
</p>
</div>
-------------------

and the outcome is:

-------------------

ABC
1
DEFGHIJK

ABC
2
DEFGHIJK

ABC
3
DEFGHIJK

ABC
4
DEFGHIJK

-------------------

I just take Good News Translation (not Greek New Testament) as an example for the merged verse. I am doing a Chinese Bible module. Thanks.

Hmmm, ok, can you give me an example in a currently published SWORD module where this is occurring? I have fixed all known occurrences of this in our own modules, so it would be interesting to compare how it is done there with what you are doing? I wonder if it has something to do with you wrapping the verse in a paragraph tag? Could you please repeat your test without the <p> & the </p> in there and see what happens?

I found it works well in The sword project but failed in Andbible, pocketsword and Bibledesktop.
Let me try to remove the <p> and see what happens.

Did you try removing the <p>? And did it work in Xiphos? I have fixed this now but it won't appear in the App Store for a while. I'll move on to your other issues now.

It was repeating the heading only, not the verse, but that is now fixed.

please test in v1.4.2, now available on the App Store.

Nic,
It is possible to switch to commentary by touching verse number and choose "see in the commentary" so this jira is a very very very low priority.
Sorry for having created it.

Could you close it?
Tanks and regards.

closing, as suggested by Ngon Cyrille
Currently the idea is that you can tap on a verse and use the "switch to commentary" button to directly go there. We may look into this in the future, but I don't anticipate it being implemented by me. [of course, other people are always free to jump in and help out!]

iPad2, iOS 4.3.3

Thanks for this, Mike. We are currently working on an iPad app, and hope to have it out by the end of July. Please pray for all the volunteers who are helping make it happen.

New version due out any day now, which will address this.

iPhone

ahh, that will require some optimisation of the locale code. I'll take a look and see what I can do – currently, if I load all the locales at launch time, it takes much longer for the app to launch! I've already optimised some of it, perhaps there are other bits I can improve to make this happen?

i forgot to add it to the add version and component it was 1.4.0b2

that sounds like a bit of a pain. I think I know how to fix it, but won't try for v1.4.0 – if it isn't as simple as I think it is to fix, I may not be able to fix it nicely on a mobile device...

Not going to fix, as I don't think this will be encountered in the wild (I haven't heard of anyone else encountering this, leading me to think that most people leave their phones in one language?).
If I make the history items language-agnostic then this will be solved, but that's a big "if".

iPod Touch 1st gen; iOS 3.1.x (can't look without killing the download, but it is the latest available for this device)

Okay, this is still unresolved, but I was able to work around it by using Module Maintainer mode. I downloaded MHC, ESV, LEB, WEB, NETfree modules on my Mac, started up Module Maintainer mode on my iPod, and then used Safari on my Mac to install them. The whole thing took about 10 minutes, so now I can use PocketSword. But the "easy" way is broken, at least for me. Thanks! Fred

Weirder and Weirder. I did a hard power off/reboot on my iPod Touch and tried and successfully downloaded and installed Scofield notes. Thinking things were fixed, I tried German Elberfelder 1905 bible - same stall happened, waited and waited and it did not move or complete. Tried Module maintainer mode and it installed in seconds...

That would be iOS 3.1.3, I believe.
Hmmm, doesn't sound good - and sounds really weird.
I had some ideas, but as you've explained it more, they are discarded. I'm really glad you discovered the "hard" way of installing modules & that's working.
I'll have to have a look around to try to figure out what is going on, but thanks for the detailed report - it really makes it much easier to try to figure out what's going on.

fixed in the next version, to be released very soon...

OS 4.0.1
iPhone 3Gs

fixed in b5 --> try tapping on a verse number in the Bible tab and see if that solves this. Thanks!

Sorry Nic, this doesn't resolve the issue.
It offers an alternative method of getting to the commentary, but as the bible location appears to be synchronized between the Bible and Commentary tabs you can simply click on the tab to get you there.
The problem with scrolling to the last verse in the Bible possibly applies more to the commentary than the bible itself. With the bible you still have verse numbering; not so with the commentary. You need to get the relevant portion referring to the verse to the top of the screen so that the header toggles it's number and indicates that the notes for the relevant verse has started.

I've made some more changes that will be in v1.3.2 final release. I'm not planning on releasing a new beta, so take a look in the final release and let me know what you think.

Commentaries now show their verse numbers, so modules like TSK should be MUCH easier to navigate. Also, Bibles and commentaries will be padded with newlines at the end of the chapter, so you should be able to scroll the last verse to the top of the screen. Marking this as "Fixed" in v1.3.2 (on the App Store now) and let me know if it resolves this issue. Thanks!

This has been fixed (if I understand your bug properly) in v1.3.2b1 – sorry, it's unreleased yet, but I've been doing a fairly major rewrite of some of the backend & hope to have that finished in the next couple of days.

Sounds good. Thank for all your hard work.

Argh, thanks for the detailed description, but I can't reproduce this. Have you tried this in v1.3.1? I've now added v1.3.1 to this bug tracker, so we can update the bug report if required. Unfortunately, I'm now running code that is newer than v1.3.1, so I may have fixed this since v1.3.1, but I have only been able to reproduce this bug on v1.3.0 myself.

I haven't tried it in 1.3.1. I'll give that a go, keep you posted.

Ok, I've had one report of how to replicate it in v1.3.2b1 and I replicated it myself, which was kinda exciting!
Meant I could figure out what was going wrong and fix it, so I'm really hoping it's fixed now.
I'll mark this as resolved, but if you find it again in v1.3.2 when it is released, let me know!!!

I am very much wanting to do this. In fact, I already have a Notes icon from my graphics friend. Unfortunately, it's reliant on bookmarks being fixed up and moved to the history/search tab, as you have suggested. And once that is done, I'll implement this. I'm thinking of export to DropBox or something like that - or the ability to email it to yourself. Just wanted to write a comment to say that this is planned!

After thinking about this, I don't think this will be implemented. Now that there is fast-app-switching, there's less need & I'd rather instead implement the ability for a user to create a "personal commentary" feature. If you can think up a good use-case for implementing this, please let me know, but hopefully iOS 4.0 resolved this for you?

I also am very much wanting to gain the ability to write notes to verses and subjects in pocketsword, just like how you can do in esword now. I love the ability to write notes and have verses easily accessible in them. Is this still something that can happen sometime?

@Peter
Yes, there are plans to allow notes connected to verses, take a look at http://www.crosswire.org/bugs/browse/PS-2 – the #2 issue in this tracker. Unfortunately it hasn't been implemented yet, but hopefully soon after the iPad version is up and running this will be looked at.
Thanks!

Ok, how tough is it to impliment these sort of things. I know that iphone apps are done in object C, and I have experience (I'm graduating this semester from Georgia Tech as an electrical engineer) in C and C++ and I have looked over my friend's shoulder who is working on an iphone app. If its not too much to take on for my first app work, then I would love to do a little work on it. Maybe using a code repository sharer such as mercurial?

something like https://bitbucket.org/niccarter/pocketsword/overview ?
knock your socks off
I'm currently snowed under with assignments - this semester is insane! But as soon as I can breathe I'll be doing some code cleanup for making it an universal app for iPad as well, but shoot me an email if you need some help when looking at the code?

I have decided to switch it back to the original <2616> version. It's ultra crazy when you have both morph & strong's displayed, but you're probably only going to be displaying both together for short periods of time, rather than for "normal" reading, so it should be ok.

I liked the suggestion, but instead have made every reference that is shown in that info pane a tappable link and that will open up the reference in a larger view. Let me know what you think.

Colin, I'm hoping the current solution works well for you? Let me know if not. Closing this issue now.

iPhoneOS 3.1.3

Interesting - thanks for the bug report. Found the issue, will be fixed in the next release

I believe this is fixed, let me know if you find it reappear anywhere...

I guess in that case you can hit the "close" button? I hope to redo the search screen for v1.3.1

I just tested for this again and it seems to be fixed, and I can't remember when I fixed it up.... if you find the bug is still there, let me know.

I purposely didn't add that 1st capability (in fact, I added it as a debugging feature last year, and then removed it long before v1.0 was released). I can't remember why I didn't, so I will look into this again for v1.3

For the own repository adding . . . something that needs to be done, yes, sorry about how long it's taking!

Should be all added as you requested, in the latest beta. Let me know what you think.

Hmmm, is this bug due to PocketSword not displaying headings?
Also, if you can tweak your module a tiny bit, does it still occur if it's encoded as:
<div class="sechead"><center><img src="images/netbible.jpg" /></center>The Creation of the World</div>
[note the lack of the initial "/" in the src tag]

Oh...duh. PS doesn't display headings.

OK, so that's why. So maybe this bug needs to be changed: Should offer to display headings, with an option just like displaying Strong's/morph.

Removing the initial / in the image file pathname causes grief in the engine because it fails to generate the right filename in the filtered result. This isn't considered a bug; it's that module content is considered to have a relative root.

ok, so you do need the initial "/". But, are these two modules simply not working cause headers aren't displayed? If that's true, I'll close this issue. You can add a new issue if you want headers to appear (I do want them there and am hoping to get onto it for v1.3!).

If you're tracking a separate issue for introducing heading display, then just close this one. It seems likely that my NET will display images normally once you provide headings.

If it doesn't, then I'll file another bug...

This is a headings issue, not an image display issue. still an issue, tho...

Ahh, yes, that wouldn't work. I'll look into it, thanks.

Cool. Thanks Nic! God bless!

When I redid search in dictionaries, I made sure that this would work as you expect.

I think I have fixed this for v1.3.0 As I can't read Greek, I'll need to wait and hear from those better educated than me...

I wonder if this would be solved when I add support for daily devotionals? There is a SWORD module type designed for that, but I haven't added support for that module type yet.

oh, I missed that out. That will do the same job.

The way you jump to a specific Bible reference has been reworked and will be released soon. Hopefully this will be much quicker and more convenient.

iPhone 3.1.2

I'm trying to reproduce this, but I can't. Can you confirm that it still occurs on subsequent launches of the app?

If it does still occur, can you try switching your iPhone's language to English and then back to Chinese and see if that fixes it?

Either way, let me know and I'll try to hunt down the issue & try to prevent it happening in the future.

Thanks for your reply. I tried to switch the language preference but still have problem. My iPhone is jailbreak (3.1.2 - 7D11), not sure if it is related.

I tried Japanese and French, both are ok. But Simplify Chinese and Traditional Chinese do not work. Thanks.

The way I handle both Simplified and Traditional Chinese changed between v1.2.0 and v1.2.1 and the only thing I can think of is that the upgrade from v1.2.0 to v1.2.1 didn't work properly for you, and so you didn't get the new translations. I have now modified the code to try to make sure it won't happen for future updates, which will be incorporated into v1.2.2, but for now, you could try to remove PocketSword and add it again from the App Store. Unfortunately you'd need to install your Bibles again, but I think that would probably be the quickest solution, rather than waiting for v1.2.2 to be released.
Sorry about that!

I tried to remove it and add it again from the App Store, it doesn't help. Is it possible for me to get the 1.2.0 ipa so that I can restore it manually? Thank you for developing PocketSword, it is really good.

Shoot me an email (you can use the "Email Us" button in PocketSword if you don't have my email address). Due to the security with the iPhone OS, I can't just give you the 1.2.0 ipa. But there are other options we can pursue.

Argh, sorry, found this bug.

The way Chinese is done is tricky - it can either be zh-Hans (Simplified Chinese) or zh-Hant (Traditional Chinese). But I have to handle 2 localisation methods: both the SWORD lib localisation and then the Apple iPhone OS localisation. Unfortunately, they are only semi-compatable, and I need to massage things for both types of Chinese. And there is a bug in that code that was introduced in v1.2.1, when I added the Simplified Chinese book names.
This will be fixed in v1.2.2!
Barry, you can still send me an email and I have a work around for you that will work until 1.2.2 comes out.

iPhone

Mind if you look at this one again? I really think having a continuous reading mode helps one concentrate on reading; swiping left/right kinda breaks your cadence.

In 1.2.0 I added something to the < button (to go to the previous chapter) so that it goes to the last verse in the previous chapter. I did that cause I was getting frustrated at wanting to read the last bit in the previous chapter to get context of the start of the current chapter.

I'll take a look at this again soon, but it won't be for 1.3.0, sorry.

Sounds good enough for me. Thanks!

I was just thinking, how about putting a marker that separates a chapter, like making the first verse marker a drop cap or putting a line between chapters? Or adding a goto button that brings you to the beginning or end of a chapter? Haven't really thought about it much, just thinking out loud.

Thinking about v1.4.0 & looking at the remaining items here, saw that I didn't reply to you - sorry! Did you know you can tap on the time, at the top of the screen, and that lets you jump to the top of the chapter? I'm not planning on thinking about this for v1.4.0 – let me know if you're still interested in this feature in a possible future release...

I'm going to close this, as I don't think I will implement this. Instead I have added swipe-to-progress (either forwards or backwards) & going backwards will take you to the last verse in the previous chapter. If there's enough support for continuous progression, I'll look into it, but I don't think it's too much of an issue.
thanks!

Ipod Touch

I'm looking into this right now, but I can't reproduce it. I'm looking at TSK and using the ESV as the Bible. What is the Bible that you currently have open in the Bible tab?

I tried to send this the other day. Sorry for delay. I just tried it w/ kjv, net free, esv. All reproduced it. Maybe I was not clear. I open bible to psalm 1:1 and then go to TSK and it displays cross refs as in this copied and pasted from TSK at Psalm 1:1:
------------------------------------
A.M. 3560. B.C. 444. Blessed.
2:12; 32:1,2; 34:8; 84:12; 106:3; 112:1; 115:12-15; 119:1,2; 144:15
------------------------------------

When you tap 2:12, the popup window displays the following that I pasted from the popup window:

------------------------------------
Genesis 2:12: (The gold of that land is pure; pearls and lapis lazuli are also there).
Genesis 32:1: So Jacob went on his way and the angels of God met him.
Genesis 32:2: When Jacob saw them, he exclaimed, "This is the camp of God!" So he named that place Mahanaim.
Genesis 34:8: But Hamor made this appeal to them: "My son Shechem is in love with your daughter. Please give her to him as his wife.
Exodus 34:12: Be careful not to make a covenant with the inhabitants of the land where you are going, lest it become a snare among you.
Deuteronomy 3:3: So the LORD our God did indeed give over to us King Og of Bashan and his whole army and we struck them down until not a single survivor was left.
1 Samuel 29:1: The Philistines assembled all their troops at Aphek, while Israel camped at the spring that is in Jezreel.
1 Chronicles 13:12: David was afraid of God that day and said, "How will I ever be able to bring the ark of God up here?"
1 Chronicles 13:13: So David did not move the ark to the City of David; he left it in the house of Obed-Edom the Gittite.
1 Chronicles 13:14: The ark of God remained in Obed-Edom's house for three months; the LORD blessed Obed-Edom's family and everything that belonged to him.
1 Chronicles 14:1: King Hiram of Tyre sent messengers to David, along with cedar logs, stonemasons, and carpenters to build a palace for him.
Job 21:1: Then Job answered:
Job 21:2: "Listen carefully to my words; let this be the consolation you offer me.
Psalms 102:15: The nations will respect the reputation of the LORD, and all the kings of the earth will respect his splendor,
--------------------------------------
You will see that what pops up does not correspond with TSK in some instances. It should have opened Psalms 2:12, not Gen. 2:12,etc. as listed in TSK at Psalm 1:1. It seems that it cannot read those tags for the present book that have no book designation (i.e Ge, Ex, Le, etc) and sends them to Genesis or to a number corresponding to a book. I don't know if this helps or not. Again, thank you for the program. I had a great time this morn with Calvin and Henry at Deut 32:39.

Sent from my iPod

Ahh, I have found it. I am using the TSK module from the "CrossWire 2" download source. It has fixed these issues, whereas the TSK from "CrossWire 1" has the issues you are reporting.

Sorry it took me so long to track this down! This is a module issue, not a PocketSword issue, per say. My suggestion is that you remove the TSK module from your iPod touch and re-install it using the "CrossWire 2" version.

This is a module issue, the module needs fixing. Instead, download the TSK module from "CrossWire 2".

Discovered that even tho this is a module issue, there is something I could be doing better in order to work around this. Have implemented that for the next release, so the TSK from CrossWire 1 will actually behave correctly.

Was able to use the previous workaround you suggested. Thank you again. Really enjoy this program.

Ahh, I did it this way for speed, before I knew what sort of load the device could take. After testing this doing it the way you expect, I discovered speed isn't an issue, so I've fixed this and will behave correctly in the next release.

In v1.3.0 there is support for Daily Devotionals. If you go to the Xiphos download section, there are some reading plans you can download. I don't have any plan to add editable reading plans just yet, so I hope this will suffice? Or you could look into creating some of your own reading plans in the same format & we can add them?

Yeah, looks great. I'm not sure about creating my own reading plans though...

I'll consider adding specific reading planner functionality in the future, but right now I'm not going to think about it. The Daily Devotional functionality shall suffice for the time being.

ahh, thanks for the reminder about this! I had forgotten about this... will look into it...

oops, finally fixed this bug. Sorry it took so long!

Hopefully the lack of Spanish in some areas has been fixed for v1.2 (live on the app store)?
But, the places where it's cut off . . . I'll have to look into that, thanks!

Sorry it's taken so long to look at, but I've changed the font size and it should now fit! Also, even if it doesn't fit properly in portrait mode, it should fit easily by switching to landscape mode. Let me know if there are any more issues... Thanks!

Let me know if you find any other places where the text doesn't fit.

You made me laugh. This is a bug that I reported in v1.0.0b2 & it's crept back in! Fixed now in 1.2.0b3. again.

iPod Touch/iPhone

Xiphos added

I'm currently thinking about what this would look and feel like . . . My thought was that if you switched to landscape mode, it would change to full screen mode. Then you would change chapters via swiping, or to do anything else, you switch back to portrait mode.

I was thinking of having the full screen mode in both portrait and landscape mode. Tapping anywhere on the text brings up the menus. Also on the changing of chapters, what do you think about having a continuous reading mode so that all the action you need to do is swipe upward?

So, I just implemented full screen mode in landscape mode. and then realised that after all the hard work was done, it was simple to make it work in portrait mode too. So, navigation is via swipe while in full screen mode & you switch to and from fullscreen mode via a 2-finger tap & hold – how does that sound? Will be in the next beta, whenever that is...

Two finger tap? Sounds ok but wouldn't it work with just a single tap to show or hide the toolbars?

it's now a 2-finger tap, rather than a 2-finger tap-and-hold. Will see how that goes...

Hmmm, this would be because we're displaying the text using html. I wonder if we can tell it not to add that extra spacing?

It it is HTML we can do anything
i guess that both the superscript text and the lines have a certain line-height and/or top-margin.
try fiddling with those
perhaps you could lessen the top-maring of the superscripted text.

I could perhaps check out the code. I have xcode and could perhaps do some good here and there

Fixed, thanks to Christoffer's javascript...

did you find a solution to this? Had you successfully used the Swe1917Of dictionary before? Had you created the cache of that dictionary before?

i could not find a way to make it stop. Perhaps if i had rebooted the iPhone... but i reinstalled the app. and it works now. I had to reinstall al translations and modules however.
I wish i had rebooted just to test if that would have fixed it though. hmm.. hindsight...

I had used it successfully before. (when i tested the strong's search and realized that you could search on this as well)

The same thing happened again (same dictionary). I had pressed Commentary and right after Dictionary.
A shutdown of the iPhone did not solve it.

after a couple of days i re-opened the dictionary, and the "loading" state had gone away and it could be opened

Finally reproduced this myself (& saw where the bug was) . . . AFTER I'd submitted v1.1 to apple . . . so withdrew the submission, fixed it, and am now resubmitting while I type this.

Aah, very good. I have many friends that will be excited when this version comes out

If you find problems in any of the modules, feel free to add a bug report to http://www.crosswire.org/bugs/browse/MOD noting it

The "search" in the dictionary tab only searches through the list of keys, so when you type a letter while you have Strong's open, it will jump to the very last entry (it does a string compare, FYI).

I have no plans to add search to dictionaries at this point, so I'm going to close this bug and say it works as intended – please comment if you're not happy with that!

I tired (after writing this first post) to do exactly the same, and it worked without problem

when i think of it, in the firt post i had kjv open and not a swedish translation... (the second time i tried i saw that it indeed was kjv)

i LOVE the search function! and how the the results are shown

I'm glad you like it
Doesn't sound like a nice bug, will look into it.....

Thanks for the report, I could never reproduce this, and I haven't heard of this issue from anyone else, so I'm tempted to think it was a bug in the 1.1.0 betas that I have since fixed.

I'll look into this after I've added better support for Strong's & while I'm working on the new bookmarks system. However, I can't promise anything right now!

I think this is beyond the scope of a "bookmark". Instead you can search for a strong's number, if you want? I'll be fixing up the UI for searching in v1.4.0, after v1.3.3 is released (which is basically just full-screen mode & landscape mode). Thanks.

When bookmarks are in folders, you'll be able to set a highlight colour for that folder, so you can quickly and easily see if a verse is "highlighted"/bookmarked. Hopefully that will be sufficient, and then you can go look at your bookmarks to see related verses? Eventually, you'll be able to add notes to verses, where you could also have your own cross-references if you'd like, so I'm not planning on implementing this issue, sorry.

With the folder you last added to pre-selected so that it would be only a few actions to add a bookmark as you are stydying a certain topic

This was added in v1.3.2 & I forgot to resolve this issue. When folders are implemented, it will then ask you where you want it saved to.

hrm.. forgot to add it to the bookmarks component.
also, i'm not sure if it was correct to create subtasks or not...

bookmarks may be added to a folder & a colour assigned to that folder. all verses bookmarked in that folder are then highlighted.

hrm.. forgot to add it to the bookmarks component.
also, i'm not sure if it was correct to create subtasks or not...

Decided that instead of showing the verse with the bookmark entry, instead you can give it a "name" or description to help distinguish between different verses (along with the Bible ref displayed)

When new bookmarks are added, the list could be scrolled down because when the list gets longer than the screen, you aren't 100% sure that it was added or not when you don't see it added in the list.
Also, exporting a set of bookmarks would be needed (also saving a set). Perhaps a mail function that would send the verses (with the verses printed out) to your email as a start.

(I am typing this on my iPhone, accidentally pressed submit while giving it a topic)

In a bookmark list it would be good to be able to see the whole verse and arrange the order ov the verses.
If you would be able to create bookmark "sets" or "folders" (that would have a name) and new bookmarks would be added to the one that is open right now and you could rearrange them, see the whole verse and export sets there would not be a need for tabs anymore.

This funktionality would make this app THE best!
(when I was testing it now I was "in a flow" with great scriptures that related and talked, I wish I had a way to get it in my notes or computer)

I would fancy something like this for the bookmarks.
Where you can create folders (and name them)
and when you add a bookmart it goes to the open bookmark folder.

It there shows the text of the verse too.
And you can rearrange the bookmarks in the folder. Also you can export the bookmark set, for instance via email

Another note regarding bookmarks.
Now it consists of a list of passages, but you don't really know which passage was which until you open one.
So you might need to go through several to find the one you wanter to dig out.
It would be good to have, if you clicked one to get to a passage, to have that same verse slightly highlighted when you come back to bookmarks so you know which one you just viewed.

This is several requests in one
I've now added a bookmarks component so you could add separate bookmarks requests to that component?

• Folders are a great idea.
• I'm hoping to change how you "add" a bookmark so that you touch the verse number & it asks you what you want to do: with one option being to add a bookmark (& then it could ask you which folder to save it to!)
• I like your idea of displaying the verse text: similar to how you see search results? Now that I've coded that, it could be easy to pull it across to bookmarks too.
• export has been suggested by others, with the main request being to sync with MacSword. However, email could be an easy place to start!

redone bookmarks for v1.4.0 & hopefully it includes all you have mentioned in this "issue"?

There is a JavaScript method that is meant to do this but it doesn't currently work on the iPhone (at least, when I tried using it in November). Instead I had to hack a method to work & this is what I came up with. It works, but simply doesn't update while you're still scrolling.

If you want to jump to a specific verse number, you can always tap on the ref title & select the verse number there? Especially useful in getting to high verse numbers in chapters like Psalm 119!

let me know what you think?

I could have a look at it if you want, i have been coding JavaScript for the iPhone at work. It's what I do. For web apps though.
Since the iPhone doesn't have a mouse the mouse related javascript handers are a little different. But it is adaptable.

I'll shoot you an email

If this is still important, please let me know. If you can provide sample code, I can go ahead with this, otherwise I'm not going to work on this...

i also suggest, but this could be debatable, that if you just add one word (love), it would be equivalent to (love*)

quite interesting slides about mobile search
http://www.comp.lancs.ac.uk/~rukzio/mobilehci2009tutorials/Jones_MobileSearch.pdf
from the MobileHCI09 conference

this was also presented at MobileHCI09
http://research.microsoft.com/en-us/um/redmond/groups/cue/phrasebuilder/
regarding A Mobile Real-Time Query Expansion Interface.

a solution could be to write -> loved && one

searching for love will give results for that word only. love* needs to be explicitly requested.

I admit that this words differently to how google search works, so it may not be entirely familiar to everyone, but in the next version I am planning on adding extra features that will make it even less like google search, so I'm not too concerned right now.

Thanks for those links

How about changing the layout of the search? Tapping on the search button would show a textbox. Below the textbox are the options "Any word" and "All words". What do you guys think?

I was also thinking of adding a new button "Advanced Search" which give the user more options like searching only OT, NT or specific books, or searching Strong's numbers, etc. I know it's a little off topic but I'm just thinking out loud.

I'm thinking the solution to this is to redo the search tab. I was about to start on it just then, but remembered that v1.2 is meant to be strong's numbers ONLY, and I don't want to delay the release even more by adding yet another change! I am scheduling this for v1.3... If you have ideas for switches/multi-switches for this new search, please add them as comments! so far I have:

"any word" vs "all words" (basically, is the search an OR or an AND search)
OT vs NT vs custom (custom will allow some sort of selection of specific books)

go wild with brainstorming – as long as you won't be hurt if you suggest something and I don't add it...

ps: thanks for the suggestions!

Minimising input and allowing the most used scenario to be as streamlined as possible.
When i have used the application, i have -always- needed the search to try to find a specific passage that i remember in my head, but don't know where it is. so i have had to type the AND between each word that i want to seach with.

I usually, when i search, if i rember some unusual words use them. often only two and that usually finds me the right passage instantly.

I would really like that the default mode would be an:
"OR" search in "The whole bible", byt you could then, if you want, choose to search OT or NT

Sorry, i meant "AND" search in "The whole bible" ... not "OR"

inputting the following search term and pressing"search" requires 19 keystrokes (with 3 keyboard view change) on the iphone keyboard
spirit AND dove
(and gives 3 hits, in KJV, and all referring to the passages where the jesus was babtized)

inputting the following search term and pressing"search" requires 11 keystrokes on the iphone keyboard
spirit dove
(and gives too many results, impossible to scroll through all of them to find the one i want, it would be faster to scroll through the gospels instead... but if this gave the former result, it would be very good)

and for
spirit AND revelation => 24 keystrokes | 1 hit - the one i wanted
spirit revalation => 18 keystrokes | 465 hits

spirit AND rev => 17 keystrokes | 0 hits
spirit rev => 10 keystrokes | 456 hits
spirit AND rev* => 21 keystrokes (5 keyboard change) | 9 results
spirit rev* => 14 keystrokes | too many results
spirit* AND revelation* 23 keystrokes | 1 hit - the one i wanted
spirit rev | 10 keystrokes | too many results
------

optimally, from a user perspective, it would

the input
word1 word2

would search for the same things as the current input

word1* AND word2*
----------------------------

scenario. thw holy spirit reminds you of the passage about us recieving the spirit of wisdom and revalation, and you want to read the whole context.
you want as much time interacting with God and his word instead of the application.

if we do not want to go with

"word1 word2" => "word1* AND word2*"

we could go for
"word1 word2" => "word1 AND word2"
"word1 word2" => "word1* AND word2"
"word1 word2 " => "word1* AND word2*"
"word1 word2 " => "word1 AND word2*"

i.e, and extra space character after a word would be quivalent to the * symbol
since, you anyway have the finger on the spacebar between words, it takes very fe milliseconds to press the same ey once more, instead of opening two extra panels to and to find with the eye and press the * and close the panel again.

i see that the last post didn't mane sense since the double space was stripped from the post.
let '_' assume an extra space character

"word1 word2" => "word1 AND word2"
"word1_ word2" => "word1* AND word2"
"word1_ word2_" => "word1* AND word2*"
"word1 word2_" => "word1 AND word2*"

and it would not replace the * feature, but be an alternative to it.

Thanks Christoffer, I think I need to have a switch on the search page for the "*" results:

"exact word search" vs "fuzzy search"
(or worded something similar, but basically, add a "*" to each word in the search).
(and, yes, if you selected "exact word search", you could manually add a "*" to words you want to be fuzzy, if you only wanted a specific word to be fuzzy.)

The exact logic of each of the buttons/switches needs to be figured out later, but getting an idea of what buttons/switches should be available is very good, thanks!

(So that makes 3 buttons/switches so far!)

[as a side note, I never use AND in my searches -- I always use && because it's quicker and easier to type and is only an additional 4 touches. But, yes, I know the search UI is sorta broken. I was really struggling to figure out how to do it "right" and gave up in the end and simply got something out there so users could search, knowing that I could fix up the UI later!]

Great discussion. I definitely agree that search is one of the features that makes me use the digital version of the Bible and keeping the keystrokes as low as possible would be great.

I recommend having these defaults on search:

• AND instead of OR
• Search both OT & NT
• "Fuzzy search"

Buttons below the search bar:

• Any (OR)
• All (AND)
• OT
• NT
• Advanced Search

; where Any and All would work like a radio button, and NT & OT would work like a checkbox (tapping both OT and NT would search the whole Scripture)

Advanced Search would have additional search options like:

• Exact word search
• Search strong numbers
• Search specific book (or range of books like Mt-Jn)

Also, I think it would be better to separate the history from the search.

I would recommend using the ranking feature of lucene, and having it turned on by default with a check box to turn it on and off. This would probably be the quickest way of getting better results, along with possibly using "AND" as suggested, when not using the ranking feature.

The motivation for the suggestion, generally speaking, people don't want to spend a lot of time typing something in to search with all the lucene search features. The ranking feature does a decent job at ranking, but still isn't perfect.

just discovered how to do a search for a Strong's Number:

search for
lemma:H0430
to search for the 430 Hebrew (note the leading H and then the extra zero at the start of the number)

search for
lemma:G652
to search for the 652 Greek (note the lack of an extra zero, but need the G).

Both need to have "lemma:" at the start.

I'm noting it here, cause I'll do this automagically when you use the "search greek strongs" or "search hebrew strongs" options -> all you'll need to do is input the number to search for (or there may be other ways of searching, too, perhaps straight from the "info pane" that appears when you touch a <S> next to a word in the KJV with Strong's)...

Another thought: Search for a Bible reference? eg: search for "Phil 4:13" and make that go to Philippians chapter 4?

I would really like to at least be able to set the default search logic. since i want to type as few words as possible, then adding another word should filter the results (i.e using the AND logic by default) to provide less hits the more you type until you have found the verse you are looking for.

AND definitely needs to be the default search mode, not OR. Beyond that, I think Ishmael's suggestions are good.

I was trying to find 2 Chronicles 7:14, from which I remembered included the phrase "If my people" and the word "humble", so I searched for
if my people humble
It took forever, to the point that I thought the app had crashed. This was, of course, because there are several thousand hits for that combination in OR mode. When it finally came up I took one look at the list and gave up on scrolling through it looking for the verse I wanted.

On the other hand, searching for
"If my people"
was nearly instant, producing one result: the verse I was looking for.

Great app, BTW. Thanks for all your hard work!

ok, have had my first stab at this. Ended up having AND as the default, fuzzy isn't on by default (but it will remember your setting each time you run PocketSword, so in the world of iOS 4.x it should remember it for a while), defaults to searching the entire Bible, you can search for Strong's Numbers, and hopefully the UI is actually quite usable.
sorry it's taken so long!

This is closely related to PS-12 & will be implemented along-side that
The 2nd point you made won't be implemented, as I'm assuming most people will be more interested in touching the Strong's numbers in the KJV/ESV/other text & having a pop-up showing the description?
If you are still interested in the 2nd point being implemented, after knowing this, open another ticket for it and I'll consider it.