While we provide the King James Version for free with PocketBible, there are many other translation options available. One of the major features of PocketBible is the ability to compare translations or create your own parallel Bible. Thus, you don’t have to be limited to one translation as you are with a printed book. This makes it easy to look at how a verse is worded in multiple translations to gain insight into its meaning.
Which Translation is Best?
Bible translations are usually categorized as to whether they provide a “word for word” translation from the original manuscripts (most accurate) or more of a “thought for thought” translation (easier to read). While the “best” translation will always be somewhat subjective, you can still find the one that is “best” for you. In addition to comparing translations for insight, you may find that you like one translation for your Bible reading and prefer another for study purposes.
Posted on: March 12th, 2015 by Craig Rairdin 2 Comments
Laridian BookBuilder gives PocketBible users the unique ability to convert virtually any electronic text into a book that can be read by PocketBible on any of our supported platforms. Whether you want to have access to any of the tens of thousands of public domain Bible reference texts you an find on the Web or you want to create original reference materials from your own studies of the Bible, BookBuilder gives you the ability to view them side-by-side with your other PocketBible Bibles and books using the same tools we use in-house to create the add-on Bibles and books you can buy at our site.
Laridian has long had a commitment to creating an open ebook ecosystem, starting with our founders’ involvement in the creation of the only industry-wide binary standard for Bible software, the Standard Template for Electronic Publishing (STEP) in 1995, and in the definition of the Open eBook Publication Structure (OEBPS) in 1999, which later became EPUB. When it became clear that a common binary standard for Christian publishing was politically impossible and that OEBPS/EPUB wasn’t interested in extensions to support Bibles and Bible reference materials, Laridian went in a different direction: Releasing as a commercial product the tools needed to create electronic books for its readers.
While most Bible software companies provide some method for Christian publishers to convert large quantities of text to their proprietary format (often for thousands of dollars per title), Laridian is one of the few (maybe the only) commercial Bible software companies to offer an end-to-end publishing solution for everyone from individual PocketBible users to multinational Christian publishing houses — and to do it for only $49.99.
BookBuilder is available for both Windows (desktop) and now for Mac OS X. The Standard edition ($19.99) contains the ability to convert tagged text to a Laridian Book for personal use. The Professional edition adds two additional tools, DocAnalyzer and VerseLinker, and gives you the option of creating a book that can be sold or given away to other PocketBible users (including hosting your book on our server for easy distribution to users of our iOS, Android, Windows Phone, Windows Store, and Mac OS X versions of PocketBible who download books from within the program). In addition, the Mac version allows users to launch PocketBible on each successful build of their book for easier proofreading.
User-created books live side-by-side with Laridian PocketBible reference books and have all the same features as the books you purchase from our site. You can do sophisticated word and phrase searches, synchronize your user-created commentary to scroll alongside your Bible, look up words in your own dictionary, link to the Bible or other reference books from within your books, etc.
As an individual user of PocketBible, you might consider these uses for BookBuilder:
Convert your PocketBible notes into a commentary. You can log into your account at our website and download a fully tagged version of your Bible notes that is ready to be converted into a commentary for PocketBible. You only need the Standard edition of BookBuilder to do this.
Convert reference material you find on the Web into a PocketBible book. This could be anything from your pastor’s sermons to classic Christian reference material that is in the public domain. The Standard edition of BookBuilder will work for this, though the additional tools in the Professional edition come in handy when working with files that you did not originally author using the BookBuilder tagging format.
Create books for distribution to others either for free or at a price of your choosing. Unlike other Christian ebook publishing solutions, there is no royalty paid to Laridian on sales or distribution of your books. You’ll need the Professional edition to do this. Note that this doesn’t mean that Laridian will sell your books, but rather that you can sell them. You can host them on our server for easy distribution, but they don’t show up in our catalog.
Books you create for PocketBible have to contain special tags that tell us how to format the book. The basic tags are what you would recognize from HTML: <b>…</b> for bold, <p> and </p> around paragraphs, etc. To those we add some special tags to tell PocketBible what kind of book it is (commentary, dictionary, etc.) and to define the book’s table of contents (which we do using HTML heading tags, not a separate table-of-contents file as you might see in some other electronic publishing formats). You do all this using your own text editor, then run the text through BookBuilder to create a Laridian Book (LBK) file. This file is then copied to the appropriate location on your device or desktop computer so that PocketBible can find it.
If you’re going to distribute your books, you’ll need the Professional version of BookBuilder. Once your book is finished and proofed, you send it to us and we’ll assign it a unique publisher ID and book ID so that it can co-exist with other books in users’ Laridian library without interfering with other books there. We’ll host it on our server and tell you how to authorize other PocketBible users to download it. This authorization is normally done manually (you log into your account and manage your books from there) or it can be automated if you have the ability to write the appropriate script for your website to send us a special command via HTTP POST. It should be noted that most people can’t do this. Generally if you’re not already confident you can do this as you read this, you can’t. But the capability is there if you need it.
Posted on: March 11th, 2015 by Michelle Stramel 5 Comments
Two of the major features of Strong’s Concordance are that it provides an exhaustive list of the words used in the Bible and it links those words back (via the assigned number) to the original language root. If you add Strong’s Concordance to PocketBible, you can search for occurrences of the root word in the Bible using its Strong’s number. We offer three versions of Strong’s Concordance for use with PocketBible: KJVEC, NASEC and HCSBEC.
What is the benefit of using Strong’s Numbers in my searches?
Some things are not apparent in the English translation.
For example, in John 21, Jesus asks Peter three questions, “son of Jonas, lovest thou me more than these?” (v15); “son of Jonas, lovest thou me?” (v16); “son of Jonas, lovest thou me?” (v17). While the KJV translates “lovest” the same each time, Strong’s assigns a different root word to Jesus’ first two uses of “lovest.” Strong’s indicates a root word of agapao (which is assigned the number 25) in the first two questions and then phileo ( which is assigned the number 5368) to that last use of “lovest.” When Peter responds to Jesus’ questions, each time he he uses the word phileo (G5368) to convey his feelings for Jesus.
You could look at the definitions for these Strong’s words and find out what others say about the meaning of these two words. But you could also explore these words in context for yourself with PocketBible. How are these two forms of love used elsewhere in the New Testament?How were they used by Jesus and Peter elsewhere? While your dictionaries may cite some verses where these words are used, the PocketBible search feature will provide you with an exhaustive list of usage.
How can I use Strong’s Numbers in my PocketBible searches?
Simply input the Strong’s number (i.e. G25 or H157) into the PocketBible search field to search for occurrences of that word in a Strong’s-numbered Bible.
To continue with our example, let’s use the PocketBible search feature to find out more about the word “lovest.” The search results presented below are from the KJV and the search is limited to the New Testament since we are talking about a Greek word. The bolded text is what is entered in the search field in PocketBible (or the syntax needed to get the results mentioned).
lovest – PocketBible reports this specific word form occurs 4 times in the KJV New Testament (KJVNT)
lov* – a second search (with a wild card) tell us that there are 202 variations of the word lov* that occur in KJVNT. The asterisk that follows the letters “lov” is a wildcard which tells PocketBible to search for all endings of the word (wildcards are not needed in the Android and Mac versions of PocketBible as they automatically report all word variations).
G25 – 109 verses in the KJVNT use this Greek word with the Strong’s number 25 (which we know from our dictionary means agapao).
G5368 – 21 verses in the KJVNT use this Greek word with the Strong’s number 5368 (which we know from our dictionary means phileo).
Thus we now know that while a form of the word “love” is used 202 times in the New Testament, only 109 of those times is the root word agapao and 21 times, phileo. That really doesn’t tell us much except to say that G25 is more commonly used in the New Testament. Given that we also want to know context for these words and how Jesus used them, we could re-run our searches and limit them to the Gospels. From there we could browse through the list to consider how these words were used in the reported verses.
For example, PocketBible reports that G5368 is assigned to the word “kiss” in Luke 22:47, referring to Judas kiss. In addition, G5368 is the root used for the word “loveth” in John 5:20 – “For the Father loveth (G5368) the Son…” So phileo is the root word used for Judas kiss and also to describe how the Father loves the Son. Hmm…this is the time I would be checking Vine’s or the Complete Word Study Dictionary to see what they have to say on this.
You can also use PocketBible to find a particular English word only when it’s translated from a specific Greek or Hebrew word. For example, love:G5368 will find all instances of the word “love” where it is translated from the Greek word 5368. To find a particular English word only when it’s not translated from a specific Greek or Hebrew word, using the format, love:-g5368, will find all instances of the word “love” where it is not translated from the Greek word 5368. To find a particular Greek or Hebrew word only when it’s not translated as a particular English word, using the format, -love:g5368, will find all instances of the Greek word number 5368 where it is not translated into English as “love.” This last search should give us Luke 22:47 where g5368 was used for the English word kiss (as we found above).