How Maqor's Interlinear Study Tool Works
Maqor presents biblical source texts as word-level study blocks. The goal is not to hide the complexity of the original languages, but to put the most useful signals close to the word being studied.
The word remains central
Every block begins with the source-language word. Hebrew and Syriac are handled as right-to-left scripts, while Greek remains left-to-right. This layout decision matters because interlinear tools can easily make the translation feel primary and the source text secondary. Maqor reverses that priority.
Support lines below the word
The word block can include IPA, a compact morphology code, a lexical identifier, and a short translation support line. These lines are intentionally short because a full explanation would make the verse unreadable. More detail belongs in the popup.
Popup detail
When a user opens the word popup, Maqor can show the lemma, lexical references, expanded morphology, pronunciation notes, prefix information, and source-specific data. This separates quick reading from deeper inspection.
Why this matters
Interlinear study can be misleading if users treat glosses as final translations. Maqor's design is meant to show that each field has a different function. A morphology code describes form. A lemma points toward a dictionary headword. A translation support line gives an approximate local sense. None of these alone replaces reading context.
What happens when a word is selected
The popup is where Maqor moves from quick reading to inspection. The verse block must stay compact so the user can read the line. The popup can show stronger detail: lemma, lexical identifier, morphology breakdown, raw source morphology, prefix information, IPA, glosses, and source-specific notes. This division is important for mobile screens, where a full grammatical explanation under every word would make the verse unusable.
Why the app separates public reading from future discussion
The current app is centered on reading and inspection. The future forum-style layer is different. It will involve claims, interpretations, denominational perspectives, academic arguments, and lay-reader questions. Those contributions need identity, attribution, moderation, and permissions. Keeping the public interlinear reader open while placing future contribution features behind login is a deliberate product separation.
How Maqor differs from a simple dictionary lookup
A dictionary entry can explain a lemma, but a verse contains surface forms. The form in the verse may include prefixes, suffixes, inflection, or spelling details that matter for reading. Maqor's value is in bringing the source form, grammatical signal, lexical pointer, and local translation support into the same visual context. That helps users ask better questions before they open a full lexicon or grammar.
How to evaluate a word card
A careful reader should ask several questions. Is the displayed original word complete? Is the morphology code expanded correctly in the popup? Does the lemma represent the base form rather than an attached prefix? Does the gloss fit the immediate clause, or is it only a rough dictionary sense? Does the full verse translation reorder the phrase? These questions keep interlinear reading from becoming mechanical.
Why the full verse remains visible
A word card is useful only when it remains connected to the verse. Maqor keeps the full verse available so users can move between the individual token and the complete line. This prevents the common interlinear mistake of treating each word as an isolated dictionary item. A word may be clear in a lexicon but function differently when it is part of a phrase, clause, or poetic structure.
The full verse also helps users recognize translation alignment limits. A translation may place an English phrase in a different order from the Hebrew or Greek sequence. It may add helper words for natural reading. It may represent one source word with several target-language words. Keeping the verse visible makes those differences easier to notice.
Why one interface serves several languages
Maqor uses one general interface for Hebrew, Greek, and Syriac, but the language rules are not identical. Hebrew and Syriac require right-to-left handling. Greek requires left-to-right handling. Hebrew prefixes must remain attached in the written token. Syriac lemmas may need transliteration normalization. Greek accent and diphthong rules affect generated IPA. The shared interface provides consistency, while language-specific rules preserve necessary differences.
For the rules behind these fields, read the methodology and the sources and licenses page.