Subscribe to Updates

Click here to subscribe to new posts by email. We use Google FeedBurner to send these notifications.

Archive for the ‘Product Updates’ Category

PocketBible and iOS 7

Posted on: September 20th, 2013 by Craig Rairdin 62 Comments

This week brings the release of iOS 7 from Apple. As this new version of the operating system rolls out to more and more devices we’re beginning to hear from you about what’s working and what’s not. I want to take a minute to tell you how to work around the one problem we know about, then tell you what we’re doing to fix that, then tell you what I think about all this. Since that flows from absolutely important to “who cares?”, you can stop reading as soon as your questions are answered.

“Go To Verse” on the iPad

iOS 7 removed a feature of “popover views” (the box that pops up out of the toolbar to show you our “go to verse” buttons) that allowed developers to specify the size of the contents they were putting in the view if that size changes after the initial contents are placed. As a result, after you choose a book, the view gets resized to its default size, and the chapter buttons get cut off.

There are two work-arounds for this:

  • Press the button in the upper left corner to go back to the list of books and choose your book again. This little bit of magic seems to break Apple’s concentration and they quit trying to resize the view.
  • Choose a different go-to method for the time being. To do this, go to the Settings menu, scroll down to Program Settings, and choose a different Bible Verse Selection method. There are two other than the book/chapter/verse buttons that are the default: The Calculator method and the Spinner method. Of the two, the spinner is the easiest to use and is less quirky. Choose the Spinner and work your way out of the Settings menu. Next time you choose Go To, you’ll see the Spinner instead of the buttons.

There are other small cosmetic issues you may or may not notice as you use the program. We don’t know of anything that affects the actual function or usability of the program beyond the one mentioned above.

What We’re Doing About It

While developers have had access to beta versions of the iOS 7 developer’s toolkit for several months, we’ve found in the past that you can waste a lot of time chasing the changing specifications of the new version of the operating system if you start your work too early. For iOS 6, many developers were stunned to discover the apps they developed and uploaded to the App Store using the final beta version (which was approved by Apple for submission to the App Store) did not function correctly on the final released version of iOS 6. They had to scramble to make changes. So with all this in mind, and after reviewing the new features in iOS 7, we decided to wait until we had a version of the developer’s toolkit that was closer to final.

We’re working on version 3.0 of PocketBible, which will be fully iOS 7 compatible. Most of the changes we have to make are user interface related. That is, tweaking colors and behavior of the UI to match the new, flat look of iOS 7. There are several new features in PocketBible 3, but these have been in beta for a few weeks now and are in pretty good shape. In particular:

  • Advanced Feature Set – New Features
    • Journal Notes allow you to take notes that are not associated with any particular Bible verse.
    • Assign names to your highlight colors.
  • Features in the Standard (Free) Version
    • Autosync feature allows you to synchronize your user data (notes, highlights, bookmarks, etc.) with the Laridian cloud automatically in the background while you continue to work. Manual sync is still available if you prefer.
    • Synchronization speed is improved.
    • Added underline styles (underline, dotted, and dashed) to the list of highlight choices.
    • Display one verse per paragraph (start each verse on a new line).
    • Support iOS swipe gestures to delete notes, highlights, bookmarks, etc. from lists of those items.
    • When deleting a bookmark category, the bookmarks themselves are deleted (instead of being moved to “uncategorized”
    • Added “Email Passage” and “Text Passage” to the list of “Passage Actions”.
    • Various speed improvements and minor bug fixes.

This version of PocketBible will be uploaded to the App Store soon. We’re still working through all the issues brought about by the release of iOS 7. In the meantime, the only thing you really need to do is change your go-to-verse method.

So What Do We Think About All This

One of the frustrations with our industry as a whole and Apple in particular is the pace at which it changes. Most of the changes in iOS 7 that affect us are cosmetic. Apple has decided that it’s their user interface, not their limited availability and high price, that negatively impacts their sales. So they spent a lot of time turning everything flat, gray, and translucent. Many of those changes are applied to programs automatically, but not all of them are implemented well.

For example, in the intrest of transparency, the system status bar (the signal strength indicator and clock across the top) is now transparent. That’s great, but our app is used to a solid status bar and would never bother to put anything behind it. Now, since that bar is transparent, the OS tells us it isn’t there and tricks us into writing under it. So when the status bar is laid over top, it just is unreadable since it’s either black or white text on top of a white page of black text. So we had to take the time to create a little colored rectangle to put under the status bar so you can see it.

While changing the look of table views (those lists of contacts, appointments, settings, etc. that you see all over iOS), they decided the headings between groups of choices should ALWAYS BE UPPER CASE. So it looks like THE PHONE IS YELLING AT YOU all the time. Furthermore, they limited the text to six lines without documenting the limit nor truncating the text. So it’s possible for text to flow over the list items. This would be fine if they provided a way to say DON’T YELL AT ME but they didn’t. So we had to implement custom text views to put in those locations.

This is all characteristic of a philosophy that has little sense of history or the importance of supporting existing apps, existing versions of the OS, or existing hardware. For example, PocketBible 3 will be compatible with iOS 5 devices, but you won’t find much, if any, mention of iOS 5 from Apple. I know people running iOS 4 and 5 who just never bother to plug their device into their PC/Mac to download updates. It’s working for them, so why bother? I’m typing this blog article on a PC running Windows XP. It works great. Why upgrade? Apple doesn’t understand this idea. They assume everyone rushes out and buys a new phone every year or two, or they at least upgrade the operating system every time an update is available.

As a result of this blindness to the past, it’s not unusual to discover that something is broken in the OS and it’s just never going to get fixed. For example, we depend on a particular method being called (viewWillDisappear:) when one of our “dialog boxes” is dismissed. I found out yesterday that iOS 7 breaks that rule (it’s been around since version 2) in certain cases. As a result, instead of one programmer at Apple fixing one bug, it creates millions of bugs in hundreds of thousands of apps, and each of those hundreds of thousands of programmers has to take an hour or two to figure out how to work around it. Apple doesn’t care because programmers who start programming new apps tomorrow will never know any differenc and will always code as if viewWillDisappear: won’t always be called, and they are the only ones who matter.

It’s as if Apple has incubation pods where they harvest new programmers. They pull them out of their drawer and they start writing code with no sense of what came before. A year later, after working 24×7 with no sleep, they are recycled to feed the next batch, which are harvested just in time to release the next unnecessary update to the operating system.

Anyway…

We’re still in the process of making changes, but this is just a couple little things we’ve run into in the process of moving PocketBible to iOS 7. We think you’ll like PocketBible 3 when we’re done, but it’s going to take a couple more weeks to get there. In the meantime, change your go-to-verse settings and 2.0.6 will continue to work fine.

PocketBible for Android 1.0.6

Posted on: July 2nd, 2013 by Michelle Stramel 47 Comments

PocketBible for Android version 1.0.6 has been released on Google Play. If you downloaded the app from Google Play, you will be automatically updated. If you are using a Kindle Fire (or other non-Google Play device), you can download the latest version by browsing to http://lpb.cc/android while on your device.

The major new feature in 1.0.6 is the ability to highlight Bible verses. It is easy to do – just tap on a verse and PocketBible will temporarily underline the verse. Choose the pencil icon from the menu to select a color and you’re done!

Along with the highlighting, PocketBible will now sync your highlights with the Laridian Cloud. So if you have highlighted verses in other versions of PocketBible, those will be transferred over to the app as well. In conjunction with this, you’ll find a new setting option on the menu for Sync Settings where you can specify how and how often your data is being synced.

While we were at it we threw in some other popular requests like the ability to view Bible verses one line at a time, set the screen in PocketBible to not time out and the ability to hide the status bar. You’ll find these new options in the Setting menus.

Updated: PocketBible for Windows Store

Posted on: June 1st, 2013 by Michelle Stramel No Comments

Windows 8 users, an update to PocketBible is now available on the Windows Store.

Enhancements to this Version 2.1 include:

  • Automatically update the application’s tile with the current book and position
  • Save and re-use multiple layouts, enabling you to save the layout (panes and books) exactly as it was and come back to it
  • New 3-pane layout option for convenient arranging of your books
  • Go to a bible verse by typing it into the verse table of contents flyout
  • Make multiple selections in the device library
  • Open one or more books directly from the device or cloud library application bar
  • Book selection context menu now displays the book titles sorted

Download PocketBible for Windows Store for free!

NOTE: Some of the features mentioned above may require the purchase of the Advanced Feature Set.

PocketBible for Android Now on Google Play!

Posted on: February 22nd, 2013 by Craig Rairdin 90 Comments

You can now download PocketBible for Android directly from Google Play. This has the advantage of giving you automatic update notifications and allows those users who cannot install third-party software outside Google Play to download the app. For those of you who have devices that do not have Google Play, you can still download the program directly from us by just entering LPB.cc/android into your Web browser on your Android device.

This doesn’t mean we’re done working on PocketBible for Android. We set a goal for ourselves of having certain features implemented prior to release on Google Play and once that goal was reached we uploaded the program. But we continue to add features. In particular, we need to get notes, highlights, and bookmarks working in the program, along with tracking of your devotional reading progress. These features will be enhanced as compared to our iOS (iPhone/iPad) version, as your data will be kept in continuous sync with “Laridian cloud” instead of requiring you to stop what you’re doing and perform a sync operation manually.

The released version of PocketBible for Android on the Google Play store should install over your “alpha” version. You shouldn’t have to delete the program before installing from Google Play, nor should you have to re-download your Bibles and books when you’re done.

The new version includes built-in help, so the old blog article that contained operating instructions will be retired soon.

We want to thank those of you who have been using the “alpha” versions of PocketBible from our site. We’ve been able to eliminate most of the major show-stopping bugs with your help.

Going forward, if you need help with PocketBible for Android, contact Technical Support through the “Help Desk” link on our website.

PocketBible 2.0.6 Available on the App Store

Posted on: October 31st, 2012 by Craig Rairdin 14 Comments

We’ve just been notified that our latest update to PocketBible (version 2.0.6) has been approved by Apple. It should become available in the App Store over the next 24 hours.

We apologize for the delay getting our iOS6-compatibility fixes into PocketBible. We ran into a couple of issues getting our update past the Apple approval process. In the end, being forced to address those issues caused us to find a couple tricky bugs that wouldn’t have turned up otherwise. But the whole process ended up taking longer than we wanted.

The complete list of new features and bug fixes is below, but a couple are worth highlighting. First, this version adds support for the Greek New Testament. You should find the SBL Greek New Testament in your list of downloadable books in “Add/Remove Books”. There are instructions in the built-in Help for enabling the Greek keyboard so that you can do searches in Greek.

Several bugs introduced in iOS 6 have been circumvented. In particular, you may have noticed PocketBible would only read the first verse on the screen to you when you asked it to start reading. This has been fixed. And it’s not really a bug, but PocketBible will now take advantage of the full height of the screen on the iPhone 5. (This wouldn’t have been a problem except that Apple “lies” to our app when we request the size of the iPhone 5 screen, apparently to maintain compatibility with apps that aren’t as clever as PocketBible by making them think they’re running on an older device.)

I believe we’ve finally fixed the problem of books and voices disappearing when memory runs low. Apple changed the way they do this a couple of times over the last year or so and kept defeating our efforts to preserve our files. We think we have it figured out now.

Finally, PocketBible now requires at least iOS 5. The latest version of the development tools only produces ARMv7 binaries and there are no ARMv7 devices that don’t support iOS 5. We’d like to support older versions of the operating system, but we’re limited by what the development tools support.

 

What’s new in this version?

  • Support for the SBL Greek New Testament including display, searching and copy/paste.
  • Added “Find Selection” to the Selection menu. Rearranged the Selection and Context menus to put more frequently used items closer to the top.
  • iOS 6 compatiblity including:
    • Fixed a bug where PocketBible would stop after one verse when speaking the text
    • Addressed rotation issues
    • Added 4″ Retina launch image and support for the full height of the new iPhone 5 screen
  • Bug fixes including
    • Fixed a bug in certain books with images where they did not appear when “shrink to fit” was selected
    • Changed the way text is selected to address sluggishness on devices with Retina displays
    • Fixed a problem that manifested in ZIBBCNT and HBH where images in tables were not shown if “shrink images to fit” was selected.
    • Made sure the built-in KJV, Help, and Welcome documents plus downloaded voices all get marked as “do not back up to iCloud”.
    • Related to the above, downloaded books and voices were moved to a folder that should not be purged under low memory conditions.
  • Set the minimum iOS version supported to 5.0.

NEW! Export, Share and Publish your PocketBible Notes, Bookmarks and Highlights

Posted on: October 16th, 2012 by Michelle Stramel 26 Comments

Are you a prolific note-taker, highlighter or bookmarker in PocketBible? We have wonderful news for you! We have a new option on our website that lets you instantly pull your personal data (notes, highlights and bookmarks) out of PocketBible for the purpose of sharing, re-purposing or turning into your own PocketBible book (with BookBuilder). Whichever you want to do!

Possibilities abound

Over the years, PocketBible users have asked for the ability to export their valuable personal data out of the program. Yes, you can now do this but we’ve taken it a step further. You choose whether you want to export your notes, highlights or bookmarks. With any of those three options, we provide you with an html file that you can:

  • Use as-is
  • Bring into a text editor and reformat and publish in a format for sharing (i.e. PDF, .doc, .txt, etc.)
  • Publish as a PocketBible book using Laridian BookBuilder program (sold separately)

What kind of book could you publish for PocketBible?

  • A dictionary of your Bible bookmarks, where each dictionary entry is a bookmark category.
  • A commentary based on your verse notes.
  • A dictionary of your Bible highlights, where each dictionary entry is a highlight color.

To encourage your self-publishing efforts, we’ve lowered the prices of both versions of BookBuilder:

There’s never been a better time to consider publishing a PocketBible book!

Getting Started

The first step is to synchronize your PocketBible data with the Laridian Server. A synchronization option is available in every version of PocketBible (except Android OS – still to come!) The second step is to login to your account on the Laridian website and choose the new My Data link. You’ll find complete information on what you can do with your data and how to do it.

Let us know what you think

We hope you like this new flexibility in using your personal PocketBible data. Is this something you will use? Let us know how you will share your writings in the comments below.

Greek New Testament Now Available for PocketBible for Windows

Posted on: September 12th, 2012 by Michelle Stramel 7 Comments


The SBL Greek New Testament is now available for use with PocketBible for Windows (versions 1.100 and later).

The SBL Greek New Testament is a new text edited by Michael W. Holmes. Mr. Holmes utilized a wide range of printed editions, all the major critical apparatuses, and the latest technical resources and manuscript discoveries as he established the text. The result is a critically edited text that differs from the Nestle-Aland/United Bible Societies text in more than 540 variation units. This new text was jointly sponsored by the Society of Biblical Literature (SBL) and Logo Bible Software to provide a free, reliable, critically edited version of the Greek New Testament for use by students, teachers, pastors and laypeople throughout the world.

The PocketBible version of this text is available for use with PocketBible for Windows, Windows PC-based Bible software which can be ordered and downloaded for free. Current users of PocketBible for Windows will need to update to version 1.100 (book reader engine version 1.071) to use the Greek text. This can be done by logging in to your Laridian account at the Laridian web site and downloading the latest version of the software.

PocketBible for Windows Updated

Version 1.100 of PocketBible for Windows includes the following updates and fixes:

  • Support for Greek books:
    • Searching
      • Added underscore (_) as a wildcard character that matches zero or more diacritical marks
      • Modified question mark (?) wildcard character to match one character and its attached diacritical marks
      • Enabled Greek character support in the search entry fields
      • Searching requires the installation of a Greek keyboard input method in Windows, which is done through the Control Panel and is fully described in the updated Help included with the program
    • Hover text (tool tips)
    • Copy/Paste
    • Added capital letters with iota subscript to Laridian Greek font
    • Normalized the order of Greek diacriticals in books, search phrases, and notes
  • Note Editor changes:
    • Added <pb_lang> HTML Helper
    • Used the font and size selected by the user for the Note Tab in the Personalization Window. Notes are now displayed and edited using the same font.
  • Other enhancements:
    • Changed the behavior of phrase searches so that punctuation between words in a book will not cause it not to match
    • Updated the Help file
  • Bug fixes:
    • Fixed a bug introduced in 1.014 where the wrong Bible abbreviation would be attached to text copied using Copy Passage (“KJVEC” instead of “KJV” and “HCSBEC” instead of “HCSB”.
    • Fixed a long-standing bug in which browsing to a new verse while editing a note with the note lock turned off would cause an error, and doing so with the lock turned on would cause the note to be saved to the current verse instead of the verse it was originally on. Also put code in place to keep user from editing or deleting a note that was already being edited.
    • Fixed a bug in which accented characters in the name of a book or Bible were displayed as HTML character entities instead of the actual character.
    • Fixed a long-standing bug in which the left mouse button appeared to be stuck down after opening or closing a book in parallel display mode. This caused text to be highlighted as the mouse was moved until the user clicked the mouse or toggled the “parallel” button.
    • Fixed a problem in which book categories were not indicated correctly for the NABRE. (May not have affected the Windows version.)

Why Have All My Books Been Updated?

Posted on: February 1st, 2012 by Craig Rairdin 2 Comments
If you’re using PocketBible on your iPhone or iPad, you may have noticed a message on the “Add/Remove Books” screen saying that many of your books have been updated. You’ll also see a similar message if you use PocketBible for Windows or one of the older mobile platforms and visit the “Downloads” page in your account at our website.

I mentioned in a recent Android update that we were going to have to rebuild all our books to support some new search features in the Android version of PocketBible. That turned out to be a 6-8 week rather than a 1-2 week exercise. Part of the reason is that since we had to touch every book that we publish, we used that opportunity to fix all the reported errors that we had on file for each book.

Many of these errors are all but invisible to the user. As a result we tend to let them accumulate for a while rather than jumping on every typo and minor formatting error as soon as we hear about it. The problem is that those things add up after a while and frankly our list had gotten overwhelming. We had one BookBuilder customer who volunteered to help a while back. He did a few books but then gave up. So this seemed like a great opportunity to just clean that list out since we had to look at every single book anyway.

In order to minimize the load on the server from everyone being told all their books had been updated, we created a way we could update the files on the server without the server thinking they had been updated. So the only time we allowed the server to know a particular book had been updated was if it was on the list of books in which noticeable changes had been made. If all we did was change “Laridian Electronic Publishing” to “Laridian, Inc.” (because one is our name and one is not) in the book’s meta data, we didn’t bother to have the server tell you about the change. But if we fixed a number of links or typographical errors — something you would notice — we had the server tell you about it.

We were also a little concerned about the load on the server if everyone went out and started re-downloading all their books. So we didn’t make a big deal about it, and we uploaded the books a few at a time over the last couple of months.

So if PocketBible or our website is telling you that a book has been updated, it means we fixed something that you might notice if you were paying close attention. In reality all the books were updated, but none of our programs currently make use of the new features that necessitated the update. So it’s only necessary to update the ones that say they need to be updated, and then you really only need to update them if you’re picky about every little typo.

PocketBible 2.0.3 Now Available on the App Store

Posted on: November 22nd, 2011 by Craig Rairdin 12 Comments

We just heard from Apple saying that 2.0.3 has been approved. You should already be seeing the update in iTunes on your device. We recommend everyone grab this update, as it fixes a few little problems. It also adds a couple of small enhancements that should make the program more enjoyable to use.

If you’re still running 1.4.7 or an earlier version you need to follow the instructions here to get this new version. Version 2.0.3 is not an automatic update to 1.4.7 or any 1.x.x version of PocketBible.


Enhancements

Double-tap on any image to blow it up in a window where it can be zoomed and scrolled. This is handy for maps and some of the detailed charts that appear in some study Bibles and reference books. It works best to go into Settings and tell it to fit images to the screen, then just double-tap them when you want to view them in detail.

If an image has links in it, those links are “hot” in the zoom view. Most images do not have links, but the maps in our Laridian Maps product do.

Books and voices are now marked as “non-purgeable” as they are downloaded. We got some reports that iOS would delete your books if it needed space for another app. This can be disturbing when you discover that books you spent a long time downloading are suddenly gone. By marking these as non-purgeable, Apple promises us they won’t delete them.

Note that while we retroactively mark your existing books as non-purgeable, and that we mark books and voices as non-purgeable as they are downloaded, we do not mark existing voices as non-purgeable due to the complexity of the file structure for voices. If you operate on the edge of available memory and want to make sure your voice files get marked as non-purgeable, you should delete them with Add/Remove Books, then download them again.

If there’s only one book open in a tab, we use that book’s abbreviation as the title for the tab rather than using the book’s category (“Bibles”, “Commentaries”, etc.) as the tab title.

Fixes

On iOS versions prior to 3.2, there were controls to allow you to turn on the tabbed interface even if you didn’t own the Advanced Feature Set. Unfortunately this didn’t really give you the full features of the tabbed interface because the rest of the program would get confused by the fact that you had tabs turned on but did not own the Advanced Feature Set. This version fixes that by hiding those controls.

Printing, emailing, or texting the selected text could crash or do nothing. This has been fixed.

We believe we’ve fixed a problem in which the text window was offset right and up so you could see the gray background behind the text window. This only happened to some users and only under certain circumstances. We could only duplicate it on one of our iPhones. It wasn’t related to which version of iOS you were running or which type of device you had (though I think we only saw it on iPhones and iPod touch devices, not iPads). What it was related to was the version of the development tools we used.

Turns out Apple swapped out a portion of the compiler that converts our Objective-C programming code into the machine code that runs on the phone. The new compiler apparently generates flawed code. (Compare to what happens when an inexperienced translator flubs up the translation of a speech at the United Nations. The original speech is fine but the translation doesn’t say what the original speaker said. That’s what happened to our code. Our code was correct by Apple’s translation of it made the device do something different.) We fixed it by turning off all the special optimizations that the compiler can do for us. Hopefully another programmer will be able to demonstrate this bug in some simple way so Apple can fix it. We were never able to do it reliably, so we couldn’t report it.

As I said, everyone should install this update. You don’t need to re-download your books or voices, nor do you need to sync your personal data after you update. This is just a normal program update that won’t affect anything you’ve downloaded nor any of your notes, highlights, or bookmarks.

PocketBible 2.0.2 Available on the App Store

Posted on: October 21st, 2011 by Craig Rairdin 14 Comments

We’ve just been notified that our latest update to PocketBible (version 2.0.2) has been approved by Apple. It should become available in the App Store over the next 24 hours.

This update mostly affects people at either end of the range of supported iOS versions. For those of you still running some version of iOS less than 3.2 (primarily those of you with first-generation iPod touch devices running 3.1.3) you’ll finally get to see what PocketBible 2 looks like. Both the initial release and the 2.0.1 update had problems that prevented them from running on those devices. We had been relying on our development tools to tell us if we were using features of iOS that were not present on those older devices. Unfortunately, it turns out they are very silent on that issue. We’ve learned our lesson and have “downgraded” an old iPhone to 3.0 for testing. (Previously we were limited to running 3.2 in the iPhone emulator.) As a result we’ve been able to identify the issues that were preventing PocketBible from running on 3.0 and 3.1 devices.

On the other end of the iOS version spectrum we ran into an interesting bug in iOS 5. When we put verses on the pasteboard (that’s “clipboard” everywhere else but in Apple Land), we always store both a plain-text version and an HTML version. This allows applications that understand HTML to paste nicely formatted text, including superscripted verse numbers, words of Christ in red, and bold headings. Simpler applications expecting only plain text have the option of requesting just the plain text from the pasteboard.

When an application pastes data from the pasteboard, it specifies what format it wants. Unfortunately, in iOS 5, when an application asks for the traditional “utf8-plain-text” that has worked in all iOS versions since the beginning of time (OK, since iOS 2), the operating system will not give it the “utf8-plain-text” version of the pasteboard text, but instead will substitute something else — in our case, the HTML text that is also there. Since the pasting application neither expects nor understand HTML, it treats it as plain text and pastes it, tags and all, into your document.

To get around this, we have to add a third form of the text to the pasteboard, which is identified simply as “text”. This version is identical to the more correct “utf8-plain-text” that has worked on previous iOS versions. Doing this tricks iOS 5 into supplying plain text to apps that request it, so that pasted verses no longer include HTML tags.

On the subject of iOS 5, it introduced some new fonts and some new ways of identifying old fonts. Since iOS makes it very difficult to determine if a font provides the bold, italic, and bold/italic versions that PocketBible requires, we use a somewhat fragile technique to try to make that determination by looking at the names of the fonts. This didn’t work exactly right in iOS 5. The result was that Helvetica Neue was displayed as condensed and bold, and both Optima and Hoefler Text were missing from the list of available fonts. This has been fixed and the code reinforced so that hopefully it will do a better job identifying fonts in the future.

Some of you have had the unfortunate experience of selecting two or three verse and when you ask PocketBible to highlight the selected verses, it highlights the rest of your Bible. This happens when the end of your selection is right on the little gap between paragraphs. This is fixed in version 2.0.2 so that your entire Bible isn’t highlighted when you only want to highlight a couple verses.

Finally, probably because of the load that PocketBible 2 has put on our servers, many of you ended up with corrupted book files. Since PocketBible can’t read the file (the were corrupted during download) it can only identify the book by its 8-character alphanumeric file name. So you would see a message that “0065001d.lbk” was damaged, but there was no way to know what book that was so that you could re-download it. This message came up every time you ran PocketBible. The new version deletes damaged books automatically so that you won’t be nagged by warning messages.

For all the complaining we do about the App Store approval process, this update was approved in about 24 hours. Hard to complain about that!

©2014 Laridian