PocketBible for Windows Progress Update #6

I was hoping to post a video update this time but if you’ve been following these updates over the last few months you know they’re doing construction right outside our windows. Today it’s especially noisy. So this is going to be a text-based update.

In the last couple of months we’ve made significant progress in several areas. I’ll go over each of these.


I demonstrated searching last time. Since then we have made it so search words/phrases are highlighted in the text and in the search results themselves.

Search results are highlighted in the text and categorized in the search results pane on the left.

If you’ve used PocketBible for Android, iOS, or macOS, you’ve seen how we organize search results into categories like “exact match”, “sounds like”, “same root word”, etc. We’ve implemented all those searches now in the Windows version. You can tap on the heading of each section of results to collapse or expand it to make it easier to navigate through the results.

Search results are displayed as they become available and a progress bar shows you how far along you are in the search.

The “did you mean ‘go to’?” result category is implemented, so you can “search” for John 3:16 in a Bible and the app will realize that you just want to go to that verse and will take you there.

In addition, there are three different “sizes” of the search results excerpts. You can display just the Bible reference, just a one-line excerpt, or three lines of the full verse.

Text Display

The program allowed you to change the font and font size before; those settings are now saved between sessions. Changing the font size affects the size of text in search results, lists of highlights/bookmarks, notes, etc.

Highlights are shown in the text. The “words of Christ” color (red here) is adjusted to maintain contrast against each highlight background color.

Note links and highlights are now shown in the text. Before you could highlight a verse and it would show up in your list of highlights, but was not shown in the text. The app automatically adjusts colored text (links, search hit, and words of Christ) so that the text has adequate contrast against each of the highlight colors. If we didn’t do this, you wouldn’t be able to see “words of Christ in red” against a red highlight background.

Note links in the text are active. Clicking on a note link shows you the note in the Notes pane.

Color Schemes

While working on highlight colors, and especially while adjusting the various text colors to make sure they’re visible against all the highlight colors, we did some work on color schemes, especially to make sure that text colors were visible against all the different backgrounds.

Color schemes are now persistent between sessions.

Create a custom color scheme. Start by copying an existing scheme.

We’ve added a custom color scheme so that you can choose your own background and text colors for various parts of the user interface. You can copy an existing color scheme then modify it. If you don’t like your changes, you can revert to your previous custom scheme.

In the process of tweaking the color schemes, we’ve defined some additional built-in schemes. We may or may not keep these.

Go To…

The Go To Verse pane works for Bibles. You can type a reference like “John 3:16” to go directly there. As you type, a list of all matching Bible book names and abbreviations is displayed to help you get the spelling right.

Go To Verse pane with list of recently visited verses.

Instead of typing a reference, you can choose a book from a list of all the books of the Bible, then choose a chapter from a list of all the chapters in that book, then choose a verse from all the verses in that chapter. PocketBible will correctly display weird chapter schemes, like the “Prologue” in the apocryphal/deuterocanonical book of Sirach and the lettered chapters that appear in Esther in some Bibles.

Any time you go to a verse or click on a link to a verse, the verse is added to a list of recently visited verses that appears in the Go To Verse pane. This allows you to quickly navigate to a passage you were previously reading. A button at the bottom of this list allows you to clear it, though it’s not necessary to every do that.

For dictionaries, commentaries, and “other” books, you will navigate via the table of contents. As of today, the table of contents navigation hasn’t been implemented, but you can type a word into a field at the top of the Go To pane to go to the dictionary entry for that word, or type a verse reference to go to the commentary article for that reference. In both cases, a drop-down list of all possible words (dictionaries) or Bible references (commentaries) helps you navigate these books.


We’ve implemented the ability to log into your account. We use that to determine if you own the Advanced Feature Set and will enable/disable features as a result. Previously we had been using a hard-wired test account.


We were really aiming for the end of the year but it’s looking like it’s going to be a little longer than that. A few unexpected and some arguably predictable factors have affected the schedule. One of our key programmers was in a car accident and suffered a concussion that manifests as an inability to focus and think clearly. This has impacted our productivity substantially. In addition, one of our outside contract programmers has had very limited availability. We’re expecting that to improve over the next couple of months.

The biggest issue is that we severely underestimated the amount of time it would take to re-write the entire program in a new language and deal with issues that would arise as a result. There are still major pieces of code (especially Advanced Feature Set features) that have not even been touched.

We’re not going to predict a new date at this point. Suffice to say it won’t be in 2021. Sorry about that. Stick with us, though — the program is really going to be good when we get it done. And as soon as we feel like we can be 80% sure of a ship date (or a beta date) we’ll let you know.


As I mentioned above, our office sits right above a major construction site. The street in front of our office has been closed for complete replacement for a block and a half in each direction. At the same time, a one-block wide, three-story tall retail/apartment building is going up across the street. This has been going on since June or July. They hope to open the street by the end of the month, then close it back down next spring.

180° panorama of the street below.

The construction project has been a source of endless surprises, such as showing up one morning a couple weeks ago to discover that there was literally no access to our building. The sidewalks were closed from both directions. Yellow caution tape was taped across our door. We discovered the secret was to walk boldly through the construction site as if you belong there, and remove the caution tape as if the danger is past. The downside, however, is that then they pour a new sidewalk right outside your door and you can’t leave until it’s dry enough to walk on.

On another day, the electricians were digging a hole for a street light foundation and augured right through the new water main in front of the neighboring building. We didn’t anticipate a problem, since one of the features of the new system is that they can shut off water to one building without affecting the others. Despite that grand promise, we were still without water for most of the day for some reason.

On a positive note, we were able to get a bike rack installed, so no more locking our bikes to whatever stationary object is convenient. Just in time for winter. 🙂

King James Version: Red Letters and Paragraphs

Title_PageBack in October, 2014 we updated our King James Version text. We had taken some criticism for publishing a low-quality edition of the text which couldn’t seem to be traced back to any known edition of the KJV.

Red Letters

When we published that version, we intentionally left out the “words of Christ in red” feature, because the whole goal was to get to a pedigreed version of the text and red letters were not a part of the KJV text until relatively recently.

This didn’t go over well with folks who rely on red ink to know when Jesus is speaking. So we did more research to see if we could come up with an “authoritative” red-letter edition of the KJV on which to base our editorial decisions. To our surprise, we found one.

In 1899, Louis Klopsch (1852-1910), editor of The Christian Herald, was writing an editorial for his magazine when he read Luke 22:20: “This cup is the new testament in my blood, which is shed for you.” It struck him that a New Testament with Christ’s words written in “blood” would be both useful and highly symbolic. He approached his mentor, Rev. T DeWitt Talmage with the idea, and the men agreed, “It could do no harm and it most certainly could do much good.”

Klopsch Red Letter BibleRight away they discovered that the KJV contains no quotation marks to delineate those words spoken by Jesus and separate them from those of the narrator or other characters in the story. It also occurred to them that there are instances in the Old Testament where it is believed that Jesus appeared to the Old Testament saints and spoke to them. Should those words be in red? What about the words of Jesus when spoken by others in the book of Acts or the epistles?

Klopsch had to make a few choices (such as in John 3:16ff) about where Jesus’ words end and the narrator’s begin. He opted to omit Old Testament christophanies, but to include New Testament quotes in red. The first red-letter New Testament was published in 1899, and an entire Bible, containing the red-letter New Testament, was published in 1901.

Laridian was able to obtain a 1903 New Testament and a 1913 whole Bible, each with Klopsch’s original red-letter text. The New Testament claims an 1899 copyright and the whole Bible, 1901. From these well-used pages we manually marked up our electronic text to indicate the words of Christ.


Soon after publishing our updated KJV last year we realized that the text we had worked from did not contain paragraph indicators of any kind. With a little effort we were able to find a source of that information that is consistent with the age and quality of the text itself, and have integrated that information into our text.

The King James Version has historically been printed with each verse starting on a new line, and a pilcrow (¶) marking the start of a new paragraph. We have followed that tradition, which means that in versions of PocketBible that allow you to display the text in paragraph form or one verse per line, you will always see the KJV text presented with each verse starting on a new line.

While some might argue that this format is jarring to the modern reader, we would point out that that KJV itself is “jarring” to the modern reader. We think there is great value in upholding the publishing traditions that add to the unique character of the King James Version of the Bible, and are very happy with the results of this effort to update our version of the text.

Most PocketBible users will see a note on the “Add/Remove Books”, “Cloud Library”, or “Download Books” screen in PocketBible to the effect that the KJV and KJV with Strong’s Numbers texts have been updated. Select the updated product to download it to PocketBible. Windows Desktop users will have to download the setup program for the KJV or KJVEC from the Downloads area of our website.

Updated King James Version for PocketBible

Title_PageWe’ve just updated the text of the King James Version we use in PocketBible. Whether you’re a devoted reader of the KJV or only have it installed because it came bundled with your copy of PocketBible, you should welcome this move to a more pedigreed version of the text.

Laridian has long been criticized for the perceived lack of attention we’ve paid to our KJV text by those for whom the accuracy of this text is a major issue. The previous version of our text was from an unknown source and contained American spellings and modern replacements for many archaic words. In some cases, these aspects of the text went unnoticed but in others they were very apparent and called into question the quality of the rest of the text.

The most commonly cited problem was our use of the word thoroughly in 2 Timothy 3:17, where the original 1611 KJV uses the archaic word throughly. While it is the case that the word throughly is defined as “thoroughly; completely”, there are some who feel the original word conveys some additional meaning that is lost by the change to thoroughly. This, despite the fact that Vine’s Expository Dictionary says “For THROUGHLY see THOROUGHLY” and even Webster’s 1828 American Dictionary says “For this, thoroughly is now used”.  This is just one example, though arguably the most significant, of about 100 spelling changes between our previous edition of the KJV and our newest release.

A Little History

The Authorized or King James Version of the Bible was the result of a project to revise the text of the Bishops’ Bible, which was the Bible of the Church of England at the turn of the 17th century. In 1604, a committee of fifty-four men were appointed to undertake the revision. Work was delayed until 1607, by which time only forty-seven of the original appointees were available to work on the project. The instructions given to the translators were to alter the text of the Bishops’ Bible as little as possible and to use the text of Tyndale, Coverdale, Matthew, Whitchurch, or Geneva when those translations agree more closely with the original Hebrew and Greek texts. The editors worked in several teams, each tackling a portion of the books of the Bible. When the work was complete, representatives of each group oversaw a final editorial pass through the text and two men worked closely with the printer to supervise the first printing in 1611.

A number of factors made it impossible for any two early print runs of the KJV to be identical. First, the printing technology at the time required that a single page be created by laying out individual pieces of type (each representing one letter, punctuation mark, or space) to create a form. Once the entire print run for that page was completed, the type was reclaimed to create the next page. By necessity, then, the second and subsequent printings of the Bible had to be re-set from scratch using the original documents or the previous printing as a guide. While errors in the previous printings could be corrected at this time, the resetting of every page made it possibile for new errors to be introduced. In 1725, printers at Cambridge University came up with the idea of making a plaster mould of an entire form, then using this to cast a metal stereotype or cliché from which identical subsequent prints could be made. This helped reduce the errors from constant resetting of the text.

A second source of variation in the text was the lack of a standard English orthography (spelling). Most people in the 16th and 17th centuries experienced reading vicariously — the actors in Shakespeare’s plays repeated his words on stage, and the clergy read the Bible aloud to the congregation. As long as the words could be pronounced in a way the hearer could understand, the spelling of the word on the page was irrelevant. It would be another 150 years before the idea of “standard” spelling and even the concept of a dictionary of the English language would come about. In the meantime, there might be two or more different spellings of the same word within one printing of the Bible (or any book for that matter).

To complicate this further, and because correct spelling simply wasn’t an issue, typesetters would add or remove letters from words to make them fit better on a line of type. This introduced another opportunity for variation.

Even after stereotyping made it possible for one publisher to maintain consistency between printings of the same book, each publisher created their own forms and thereby introduced their own changes into the text. Publishers also felt free to add or remove footnotes, change punctuation, and revise the spelling or word usage for their particular audience.

The result of all of this is that we have literally hundreds of different versions of the King James Version text on bookshelves around the world, created over a period of more than 400 years by dozens of publishers using a variety of printing techniques. Each of these is labelled “King James Version” and none come with a list of how they differ from the printing before them, let alone the original 1611 text.

The Age of Electronic Publishing

In the late 20th century it became possible for anyone with a high-speed scanner and optical character recognition software to create an electronic copy of the King James Version text — and they did. Our previous King James Version text was the product of one such person’s efforts. We don’t know which of hundreds of available versions of the KJV text they used, but we know it had Americanized spellings (honorable for honourablerazor for rasorcounseller for counsellor, etc) and modern proper names (Jeremiah instead of Jeremy or JeremiasNoah instead of NoeIsaiah instead of Esaias, etc.). It also used a number of modern words in place of their archaic counterparts (the previously cited thoroughly in place of throughlyprivately in place of privilyfood in place of meattwo in place of twain, etc.).

Laridian’s Historic Position

Because the KJV has been around for 400 years; because it lived through every significant improvement in publishing since moveable type; and because we could find no two KJV Bibles (especially from different publishers) which agreed with each other, we took the position that there was no “best” KJV text. In every case cited by a customer, we could find an example of a KJV Bible from a major publisher that agreed with our version and another that agreed with them.

Lacking an obvious answer to the question “Which KJV is the KJV?” short of the 1611 text (which nobody reads since it uses “u” for “v”, “j” for “i”, and something like “f” for “long s”, rendering it virtually unreadable), we turned to two authoritative sources. First was Cambridge University, which is the steward of the Crown’s copyright on the King James Version in the United Kingdom. During a conversation over a meal, I asked if they had electronic files for the “official” King James Version — assuming there was such a thing, perhaps in a vault buried deep under London. Had I not been paying for their dinner, I would’ve been laughed out of the room. They repeated much of what I’ve stated above, and added the fact that every publisher over the years has made their own “corrections” and changes to the text, including Cambridge itself. They could offer me no advice other than to use one of their more recent printings (for which they had no electronic files). Since that would carry no more weight of being “the” KJV than the one we already had, that seemed like a waste of time.

I next turned to Dr. Peter Ruckman, perhaps the most well-known authority on the “KJV Only” position. Dr. Ruckman argues not only that the KJV is the only accurate English Bible in existence, but that it supersedes the original Hebrew and Greek texts in any question over interpretation of the Word of God. According to Dr. Ruckman, translations of the Bible should be made from it, not from Hebrew and Greek. I wrote Dr. Ruckman a letter asking for his recommendations for an “official” text of the King James Version that would satisfy the requirements of his most vocal followers for an accurate text. Dr. Ruckman scrawled “IDIOT” over my letter and sent it back to me, with the comment “any Gideon Bible”. I pulled my Gideon Bible off the shelf and found it to be a modern English version, not the KJV at all. Of course, I don’t believe Ruckman was making the case that the Gideons were the Keepers of the Authoritative King James Version Bible Text, but rather that I could literally grab any KJV Bible off the shelf, even the free Gideon Bible I found in a hotel, and use it in our software.

When the appeal to authority failed, we simply settled into distributing the KJV that we had and left it at that.

The Pure/Standard Cambridge Edition

Once or twice a year we are contacted by PocketBible users who have a serious problem with our KJV (usually citing the use of thoroughly in 2 Tim 3:17) and encouraging us to publish “the” KJV (and threatening us if we don’t). None of these users have ever been able to point to a definitive, authoritative source for this text, but recently we were directed to two sources: The Pure Cambridge Edition (PCE) at www.bibleprotector.com and Brandon Staggs’ Common Cambridge Edition at av1611.com. Both of these sites claim to have done extensive research to produce an electronic edition of the text that matches that in use by Cambridge University Press around 1900-1910, down to the last punctuation mark, capital letter, and use of italics.

We downloaded these texts and compared them to each other. They differ in about a dozen places, none of which are anywhere near as significant as the use of thoroughly for throughly in 2 Tim 3:17. After looking at some other similar sources, we settled on a version of the text that draws mostly from the Pure Cambridge Edition except in a couple places where we felt the Common Cambridge Edition was better. (In particular, we hyphenate Elelohe-Israel and Meribah-Kadesh instead of creating the “camel-case” spellings EleloheIsrael and MeribahKadesh used in the PCE, and we chose to leave out the footers THE END OF THE PROPHETS after Malachi 4:6 and THE END after Revelation 22:21.)

It was fairly trivial to convert this text to PocketBible format. The hard part was merging Strong’s numbers into it, but we’ve done that to create an updated version of our King James Version With Strong’s Numbers product as well. This has the additional benefit of bringing these two texts into agreement with each other, as even our own KJV and KJV/Strong’s texts had disagreed in a number of places.

Lessons Learned

We’ve gained a new appreciation not just for the King James Version in this process, but also for the history of the English language and printing technology. The myriad variations on the KJV text had led us to “give up” and settle for what was easy. However, this project created the desire to produce something of historical validity and significance, even if it can’t be said to be “the” KJV.

While we don’t agree with those who argue that the KJV is the only English Bible we should be reading, we do agree that it has historical significance and that we should provide a version of it that meets with the approval of those who put it on a taller pedestal than we do. We believe this edition of the KJV for PocketBible meets that standard.

We’re considering publishing some earlier editions of the KJV just for their historical value. While we don’t find reading the 1611 text to be particularly edifying, we do find it interesting. For example:

“And as Moses lifted vp the serpent in the wildernesse : euen so must the Sonne of man be lifted vp : That whosoeuer beleeueth in him, should not perish, but haue eternall life. For God so loued yͤ world, that he gaue his only begotten Sonne : that whosoeuer beleeueth in him, should not perish, but haue euerlasting life.”

I’m particularly intrigued by the shorthand rendition of the word “the” in “God so loued yͤ world”. This comes from the Early Middle English spelling of “the”, which was þe (the archaic letter thorn followed by e). When printed in the common black letter or gothic font, thorn looked very similar to y, and printers (especially in France where thorn did not exist in their alphabet) would substitute the letter y. When needed to make the words better fit on a line, the e would be placed above the y as you see here. (Another example is the word thou which was often shortened to yͧ.) It’s easy to imagine how yͤ became “ye” in “Ye Olde Book Shoppe”, and why “Ye” in this context should be pronounced with a “th” sound like “the”.

Anyway, I digress….

You can simply download the KJV from within PocketBible if you’re running PocketBible on a platform that supports that feature, or, if you have PocketBible for Windows Desktop, go to your download account at our site to download a new installation program for the KJV or KJVEC (KJV with Strong’s Numbers).