Lexicons

What is included

All four have public-domain source records and ship inside the app. The exact source and rights basis for each is listed under Content licences. A mapping table connects Strong’s Hebrew numbers to their BDB entries, since the two systems do not correspond one-to-one — a single Strong’s number can resolve to several BDB entries for different words or homographs.

Looking a word up

In a Strong’s-tagged translation, tap a word — in the reader, in a commentary or in a book. The lexicon view opens on the entry for that word’s Strong’s number; swipe to see the same word in each of your other lexicons. A count beside the entry shows how often the number occurs, and tapping it searches for every verse that uses it.

An entry can include:

• The lemma in its original script, with transliteration and pronunciation.
• A definition, and for BDB a full article with numbered senses.
• Part of speech, and the word’s morphology code.
• KJV usage — the range of English words used to render it.
• Derivation notes.
• Scripture references, which open a preview you can page through, and cross-references to other lexicon entries.

Ordering and hiding

Hebrew and Greek each have their own lexicon order, set in Settings → Modules → Settings. The default puts Strong’s first, followed by BDB for Hebrew and Dodson for Greek. Drag them so that the dictionary you actually trust appears first, and swipe to hide the ones you never read — hidden lexicons stay installed and searchable, they just stop appearing in lookups.

Adding your own

Lexicons are dictionary modules. Any dictionary keyed by Strong’s number or by lemma can be packaged as a .lamp file and installed alongside the bundled ones; it will then appear in the lookup order and in search. The schema, including support for senses, annotations and inline media, is documented in Authoring modules.