ris3n's Apologetics Codex

Passage

Luke 3.38

Book: Luke · ASV / WEB / KJV / YLT

Immediate context (±2 verses)

There are ads on our codex that pay for hosting and keep the codex free. If you can, please consider whitelisting ris3n.com or allowing scripts to support the work.

Sponsored

ASV (ASV)

"36. the son of Cainan, the son of Arphaxad, the son of Shem, the son of Noah, the son of Lamech, 37. the son of Methuselah, the son of Enoch, the son of Jared, the son of Mahalaleel, the son of Cainan,"

"38. the son of Enos, the son of Seth, the son of Adam, the son of God." (Luke 3:36-38, ASV)

WEB (WEB)

"36. the son of Cainan, the son of Arphaxad, the son of Shem, the son of Noah, the son of Lamech, 37. the son of Methuselah, the son of Enoch, the son of Jared, the son of Mahalaleel, the son of Cainan,"

"38. the son of Enos, the son of Seth, the son of Adam, the son of God." (Luke 3:36-38, WEB)

KJV (KJV)

"36. Which was the son of Cainan, which was the son of Arphaxad, which was the son of Sem, which was the son of Noe, which was the son of Lamech, 37. Which was the son of Mathusala, which was the son of Enoch, which was the son of Jared, which was the son of Maleleel, which was the son of Cainan,"

"38. Which was the son of Enos, which was the son of Seth, which was the son of Adam, which was the son of God." (Luke 3:36-38, KJV)

YLT (YLT)

"36. the [son] of Salah, the [son] of Cainan, the [son] of Arphaxad, the [son] of Shem, the [son] of Noah, the [son] of Lamech, 37. the [son] of Methuselah, the [son] of Enoch, the [son] of Jared, the [son] of Mahalaleel,"

"38. the [son] of Cainan, the [son] of Enos, the [son] of Seth, the [son] of Adam, the [son] of God." (Luke 3:36-38, YLT)

Setting

  • Speaker: Luke the physician (traditionally) / narrator + Jesus's direct teaching
  • Audience: Theophilus + Gentile Christian audience (companion to Acts)
  • Location: first-century Palestine (events); composition possibly Caesarea or Rome
  • Time period: events c. 4 BC, AD 30/33; composed c. AD 60-80

Theological reading

Key words

Quoted in

Why these four translations

ris3n chose ASV, WEB, KJV, and YLT for two reasons together. They are the most literal English translations available (formal-equivalence: word-for-word renderings that preserve the Hebrew and Greek grammar rather than smoothing it into modern dynamic-equivalence idiom). And they are in the public domain in the United States, which means fair-use quotation at any length requires no publisher license. Modern licensed translations (NASB95, ESV, NIV) restrict volume of quotation under their copyright terms, so they are not used at stub-level coverage here. NASB95 appears only on hand-curated rich passage hubs under Lockman Foundation's fair-use allowance.

The four:

  • ASV (American Standard Version, 1901). The basis of the modern critical-text English tradition.
  • WEB (World English Bible, contemporary). Public-domain revision in the ASV line, in current English.
  • KJV (King James Version, 1611). Reformation-era, Textus Receptus base.
  • YLT (Young's Literal Translation, Robert Young, 1862). Hyper-literal preservation of Hebrew and Greek grammar; useful for word-study work even where English reads stiff.

See Bibles for the full per-translation history, translators, textual basis, strengths, and weaknesses.