Interface with other Bible versions

Donna Whisnant — Sun, 05 Oct 2025 16:47:34 -0000

For this topic, it's best to discuss via private email, rather than to have it posted here in the SourceForge discussion forums. In the KJPBS, go to Help->About (or press F1) to bring up the "About" dialog. On that dialog, click the "License" button at the bottom to bring up the "License" dialog. On that dialog, locate the URL for my personal website near the bottom where it says "Contact". Use that URL to navigate to my personal website. On my personal website, click on the "Contact" link at the top navigation bar. Use the details there to locate my private email address and use that to email me directly.

Interface with other Bible versions

Donna Whisnant — Fri, 03 Oct 2025 17:05:14 -0000

The KJPBS code search logic isn't tied to a specific Bible translation, but legal copyrights and such prohibit supplying the data for those other translations. This tool's primary purpose is to explore the numerical patterns in the King James text and not so much a generic Bible reading/study app. Most all of these other Bible translations require licensing, and in some cases usage fees, with the copyright holders and as such isn't in the scope of design for this app.

Other users have, however, taken the data for other translations and have used the KJPBS code search logic to compare numerical patterns in these other Bible texts to prove that the King James is the only one that's divinely inspired. To do this, you would need to build KJPBS database files for the desired text you wish to explore.

While the KJPBS database format is unique to KJPBS and is purpose-built for doing numerical counting of the text, the source code for the app, as posted, has tools to convert from upstream OSIS (Open Scripture Information Standard) XML format into KJPBS format and is how the data for the King James text in this app was created. You could compile the KJPBS source yourself and use those tools to create whatever source data you wish to search.

In short, the data for a specific Bible text is converted into a list of unique words with per-verse templates on how to render the text. The actual human-readable text isn't in the KJPBS database files, as KJPBS doesn't actually do any "searching". It already knows exactly where every word in the text is located and the app is simply a filter that lets you view those counts for specific words and sequences of words from the text. In other words, you can't just give it a giant text file and have it do word counts from that text. All of the counting is actually done in the process of making the database file for KJPBS and the app is just the tool to view it.

Interface with other Bible versions

Bruce Davenport — Mon, 29 Sep 2025 18:02:21 -0000

    Are there versions of this GUI that can interface with other Bible versions ie Catholic, NIV, JW etc

LINUX UPDATES

Donna Whisnant — Thu, 28 Aug 2025 16:59:42 -0000

Thanks for the input. What you outline for the "Fix on end-user machine" I have had posted on the purebiblesearch.com website instructions for quite a while now.

And yes, Linux distros have been steadily moving away from LSB, and KJPBS has been moving away from it too. The current "official production release" of KJPBS, as posted on purebiblesearch.com, is about 12-years old now.

My newer releases of KJPBS are moving away from a system-package style installer, which used LSB to meet system package dependencies, to use an AppImage instead. Alpha-Snapshot releases of it are already available, which also include many new features that have been added to KJPBS over the last 12-years, such as ELSSearch, for example.

These Alpha-Snapshot releases are posted on my GitHub KJPBS repo, rather than SourceForge. Ever since the Chaos Monkey got loose inside of SourceForge, I have diversified the KJPBS source to have multiple hosts, like GitHub, in addition to SourceForge. However, posting of release snapshots is generally more convenient on GitHub and so that's where I've been posting them instead of on SourceForge. The source code, however, is sync'd and pushed to all of my upstream repo hosts.

You can find the snapshots at this link: https://github.com/dewhisna/KingJamesPureBibleSearch/releases

Simply follow the instructions posted there for each platform. For Linux, it's really just a matter of making the AppImage executable and running it. There are, however, a few notes on how to copy over some of the features in the Windows and MacOS alpha-snapshots into the Linux one, if you want to experiment with all of the latest features. This is needed because the Linux build is built via CI on a Jenkins build server and only includes things formally released to source control, whereas the Windows and MacOS snapshots are still hand-built and include things like experimental databases that aren't formally released yet.

In any case, these snapshots are much newer than the "official release" on purebiblesearch.com, with the latest snapshot being from June 28, 2025, so just a few months ago.

LINUX UPDATES

james — Thu, 28 Aug 2025 16:09:14 -0000

Subject: Pure Bible Search – Linux LSB Loader Issue Caused 404 / “File Not Found”

Dear Sir / Madam,

I recently installed King James Pure Bible Search on Ubuntu 24.04 using the
“.run” package (kjvpurebiblesearch-3.0.0-2.x86_64.run).
Everything extracted cleanly, but on attempting to launch the program I
received:

bash: ./KingJamesPureBibleSearch: cannot execute: required file not found
ldd revealed: /lib64/ld-lsb-x86-64.so.3 => /lib64/ld-linux-x86-64.so.2

Modern glibc distributions (Ubuntu 22+ and derivatives) no longer provide the
“ld-lsb-x86-64.so.3” symlink that your binaries link against.

Fix on end-user machine
- sudo ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

Permanent fix for future releases
- add a single linker flag at build-time:
g++ … -Wl,--dynamic-linker=/lib64/ld-linux-x86-64.so.2
or in CMake:
set(CMAKE_EXE_LINKER_FLAGS "-Wl,--dynamic-linker=/lib64/ld-linux-x86-64.so.2")

Using the standard interpreter removes any dependence on the deprecated
LSB loader and eliminates this error for all current and future Linux users.

Would you consider applying the flag in your next build?
Thank you for producing this excellent piece of software.

Kind regards,

James

ELS new feature

Donna Whisnant — Tue, 01 Jul 2025 02:19:06 -0000

Correct. The pre-production alpha snapshot versions of KJPBS are posted on GitHub instead of SourceForge. Here's the link where they can be downloaded:
https://github.com/dewhisna/KingJamesPureBibleSearch/releases

As of this posting, the latest snapshot was two days ago on 2025-06-28.

You can also check the exact version of KJPBS you are using from the "About Box" in the app. Alpha snapshots will be labeled with something like "v3.0-1358-g03692d23", which means 1358 code commits past the v3.0 tagged release at the git hash that starts with "03692d23", which can take you to the exact point in the source code for that release.

ELS new feature

Neal Ryan — Tue, 01 Jul 2025 00:13:31 -0000

English ELS new feature added. To access go to 'Window' on the new version. It will show up under 'Open Search Windows'. If there is nothint under 'Open Search Windows' then it is not the 2025 version of KING JAMES Pure BIBLE Search

Error in the 1611 Online database

Dale Franklin — Sat, 29 Mar 2025 04:41:10 -0000

Hello there, just reporting a discrepancy in the 1611 online database. It has James 1:22 as "receiuing" rather than "decieuing". The this would be the 66th mention of "decieu*" by the way lol.

The Apocrypha: Feature Request

Dale Franklin — Sat, 29 Mar 2025 02:37:15 -0000

I humbly second this request and in the order that it is given in the 1611/1769.

Counts of the Italic Words

Kimberly Palmer — Wed, 08 Jan 2025 04:09:05 -0000

Thank you, I'm going to try it first before I bother you further. Thanks so much.

Recent posts to Discussion

Interface with other Bible versions

Interface with other Bible versions

Interface with other Bible versions

LINUX UPDATES

LINUX UPDATES

ELS new feature

ELS new feature

Error in the 1611 Online database

The Apocrypha: Feature Request

Counts of the Italic Words