Donna Whisnant

You are correct that the current "official" release of KJPBS is only Intel architecture. However, that release is about 13 years old. A new "official" release hasn't been created in some time now due to the massive amount of work involved in doing so. However, if you use the current Alpha-Snapshot release of KJPBS, it already supports the ARM64 (aka "Apple Silicon") architecture. Being an "alpha" version, doesn't mean it's buggy or is missing any significant functionality. It means that I haven't...

Feel free to submit a new icon for the app to use for that mode. As they say in the open-source world: "Pull Requests Welcome"... though if possible, please submit it on the GitHub mirror site https://github.com/dewhisna/KingJamesPureBibleSearch

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...

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...

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...

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...

If you get too lost and confused on figuring out how to run KJVDataDump, go to my personal website (dewtronics.com) and click the "Contact" option in the menu. Use that to send me a private email message and I'll send you a text file with the italic words extracted.

Well, the main KJPBS app itself does not, mainly because of how the italicized words are stored and processed. The "italicized words", which are technically known as "translation added/changed" words, are done via markup in the per-verse templates of KJPBS and aren't otherwise delineated. KJPBS doesn't have the actual human-readable Bible text, but instead has a list of all unique words and their numeric position within the text. Each verse has a template that tells it how to take that list of words...