Problem: Strong's definitions alone are often terse. The KJV usage data shows how a Greek/Hebrew word was actually translated across the King James Bible — providing practical, real-world translation context.
Solution: Integrate KJV usage data into the interlinear popup, powering both the gloss extraction and the "Translated as" frequency explorer.
Not included: A standalone KJV concordance view. This is integrated into the interlinear popup.
KJV usage data powers two parts of the interlinear popup:
extractGreekGloss() and extractGreekMeanings() parse the kjv_usage string to generate short glosses and meaning chip alternativesCurrent state: Fully functional for Greek. Hebrew drill-down not yet implemented.
Already integrated into the interlinear expanded word card UI. No separate view.
Data: strongs_greek.kjv_usage and strongs_hebrew.kjv_usage columns — text strings like "love(86), beloved(47), charity(27)"
Usage in code:
extractGreekGloss(kjv_usage) → picks the most common translation as short glossextractGreekMeanings(kjv_usage) → parses up to 12 alternatives for meaning chipsFiles:
apps/web/src/lib/utils/text.ts — parsing functionsapps/web/src/routes/api/interlinear/translations/[strongsNumber]/+server.tsCurrent: IN_PROGRESS Milestone: v2
What's done:
What remains:
Dependencies: