The mother of the first children is named in a way that keeps its connection with the Hebrew narrative audible.
Read in the Bible →The Way Version.
More than original names.
What happens to a saying when it moves from one language into another? Yeshua (Jesus) taught in an Aramaic-speaking world. His words were heard in the rhythms, images and cultural setting of everyday speech. The Gospel tradition reached readers through Greek writings and centuries of translation. A word-for-word equivalent can carry the basic sense while leaving an idiom, a poetic association or a social nuance harder to hear.
The Way Version is a complete, 66-book English Bible and a continuing source-grounded investigation into those questions. Original names make the history visible. Original meanings are the deeper work: comparing language, context, textual witnesses and interpretations so that an English reader can see more of what the passage communicates.
See how Eve appears as Havvah, how the disciples' names read, or why Ecclesiastes addresses “humanity” instead of only “man.” Each example comes from the current TWV reader.
Start with the Aramaic-speaking context · Read The Way Articles · View open questions
Eve becomes Havvah. The disciples have names with histories.
The earliest noticeable difference is who appears by name. Earlier-language forms reconnect familiar figures to the worlds in which their names circulated. Havvah is the form TWV uses for Eve, alongside Adam and their children Qayin (Cain), Hevel (Abel) and Seth. Genesis 3:20 associates Havvah with the “mother of all the living.” Naming can retain historical texture without pretending an English form names a different person.
The same experience continues into the Gospel accounts. Jesus is Yeshua; Simon Peter appears as Shimon (Kepha); James as Ya’akov; John as Yochanan; Thomas as Ta’oma; Matthew as Matai; Judas as Yehuda. Some names are Semitic; others, like Andreas, reflect the multilingual setting. TWV follows the actual forms chosen in the released text, rather than imposing one rule on every name.
The brothers' names are visible within the same story, not merely explained in a detached glossary.
Read in the Bible →The list of disciples reads differently when familiar English renderings no longer conceal their shared naming history.
Read the names →The surrounding names show that the project is not limited to replacing “Jesus” with “Yeshua.”
Read the names →Reader option: The Way Version is the translated text. The Bible with Original Names is its free reading edition and app. Keep earlier-language names visible, or switch to familiar English forms without switching the underlying translation. The original-name coverage issue documents ongoing efforts to keep every released name and reader glossary entry consistent.
A language carries more than a dictionary definition.
In the Aramaic-speaking world of Yeshua, a short phrase could carry tone, rhythm, metaphor and cultural associations familiar to a listener. Bringing such speech into Greek, and later into English, involves choices about which shades of meaning to make explicit. This is a normal challenge in translation, not something unique to ancient texts.
Consider South Korea. Some of the project's research team work from there. Korean 눈치 (nunchi) might be introduced in English as “reading the room,” but the Korean expression also includes sensing interpersonal cues and adjusting appropriately. The English phrase is useful, yet the association is not identical. Academic work on nunchi confirms that cultural context affects how people interpret it. Ancient Aramaic speech can raise similar questions when an idiom is expressed in another language.
The Greek Gospels themselves sometimes preserve an Aramaic expression and then explain it. In Mark 5:41, TWV retains “Talitha cumi” and gives its meaning, “Girl, I tell you, get up.” Mark 3:17 gives the nickname Boanerges and interprets it as “Sons of Thunder.” The original expression, the translation and its literary context all tell us something.
The surrounding scene matters.
What does the phrase do in the passage? An idiom, name, image or metaphor cannot always be understood by matching isolated dictionary entries.
Aramaic, Greek and Hebrew contribute differently.
Aramaic helps situate the sayings of Yeshua; Greek manuscripts are crucial for the Gospels; Hebrew witnesses matter for much of the earlier Bible. Syriac traditions are useful comparators.
Ask what each source actually supports.
The Way seeks a responsible account of original meaning. Some readings are secure; others are proposed or interpretive, and the public research should make that distinction visible.
Scholarly starting points: Matthew Black explored the Aramaic speech-world of Jesus, and Maurice Casey investigated how Aramaic expressions may have been represented in Greek Gospel material. Such scholarship explains why translation is a serious historical question, not a mechanical substitution exercise.
Small changes in English can change who and what we hear.
Here are direct comparisons, not motivational slogans. The goal is to show what TWV actually puts on the page, how the wording changes a reader's experience, and which source questions are worth asking. Every TWV rendering below has been checked against the current web-reader data.
“Man” or “humanity”?
The older English sounds male-specific to many readers; TWV presents the concluding instruction as applying to all people. That broader English is not a discovery unique to TWV; it is a deliberate way of representing the audience.
Read in context →“Young man” or “young person”?
The passage's instruction need not sound limited to men. The Way's recurring use of “person” invites women and men to recognize themselves in a shared wisdom tradition, while source-language claims remain passage-specific.
Read in context →Who can understand the work of Elohim?
TWV removes a generic masculine English subject; the point about the limits of human understanding remains. That difference may be modest linguistically yet important to a contemporary reader.
Read in context →“Repent” / “kingdom” or “turn back” / “reign”?
The choice shifts emphasis from an inherited religious term to changing direction, and from a place called a kingdom to the activity of reigning. The Greek and Semitic word families have ranges; this contextual choice should be tested, not imposed on every verse.
Read in context →“God and man” or “Elohim and the people”?
“The people” lets modern readers see a wider human circle in a line often heard as addressed to “man.” This illustrates the care needed when a traditional masculine English form has a wider intended referent.
Read in context →Why retain Ruach?
The source-language word family around Hebrew/Aramaic ruach/ruha evokes breath, wind and spirit. Hebrew ruach is grammatically feminine; the original Greek passage has its own grammar. Neither grammatical gender nor a word root alone proves that the divine has a biological sex.
Read in context →“Men and brethren” or “brothers and sisters”?
A community address can include women in context even where traditional English sounds male-only. Here the change helps a contemporary reader visualize the group being addressed.
Read in context →When translation becomes interpretive expansion
TWV takes an expansive approach here rather than merely changing a name. The question is whether its imagery clarifies the historical saying or goes beyond the textual evidence. That precise boundary remains open to public scrutiny.
Read in context →The point is not that every traditional translation is wrong. English changes over time, and several modern Bible versions already make inclusive or contextual decisions. TWV makes its particular combination of original names, translation choices and open research accessible for readers to examine and challenge.
How a translation question becomes a documented decision.
The Way Version did not start from a blank manuscript. It began with the public-domain World English Bible and has evolved through investigation of names, wording, historical settings and linguistic evidence. The current 66-book EPUB and source record live in the public translation repository.
Rather than treating every proposed wording as a finished answer, the working method compares alternatives and records why a passage is changed, held, or questioned. AI assists with cross-references, searches and consistency audits; it does not replace checking the texts and historical sources.
Identify something worth checking
A name has been missed, “man” may address a mixed group, “reign” may carry a different emphasis, or a textual witness raises a meaningful variant.
Trace language and context
Consult the primary surviving witnesses appropriate to the book, compare Aramaic/Syriac patterns where informative, and examine scholarship and competing explanations.
Document candidate renderings
Specify the verse, previous wording, proposed alternative, supporting sources, uncertainties and which other passages a change might affect.
Open the question to criticism
Use the Open Issues pages, GitHub issues, research notes and outside source-based responses to test an idea before treating it as settled.
Check the wording across the whole Bible
Where a revision is adopted, review context and related cases, test book/chapter coverage and generated outputs, and keep canonical text, EPUB, website and app in sync.
Keep a reviewable history
Leave significant rationale, change logs and unresolved alternatives available. A released reading can still be questioned and improved.
Real examples in the GitHub record
Follow the editor notes, change logs, current release and earlier editions yourself. These records are part of what distinguishes an inspectable ongoing investigation from a page of unsupported claims.
Research you can read, check and question.
The Way Articles looks at biblical language and history with care for what the evidence can show. Read about the Aramaic-speaking world of Yeshua, the Syriac tradition, the women and communities of early Christianity, and how the Bible reached readers today.
Articles distinguish textual evidence, historical interpretation and continuing debates, with links to sources and to the relevant verses.
Learning together, following the words to their roots.
Scholars and educators across these academic communities have engaged with questions about names, languages, manuscripts and interpretation. Their perspectives bring fresh evidence and constructive criticism to the ongoing work. The same spirit of inquiry is open to anyone with a thoughtful question, a source to share or a passage worth revisiting.
Professor Amy Peeler provided a response to examples involving Ruach, Elohim and wording in Luke's annunciation story.
Professor Rhiannon Graybill considered the choice of “woman” versus “wife” in Genesis 3:8 and the meaning lost if “his” is omitted.
Professor Marion Taylor suggested scholarship on women's readings of Genesis, name-order variants involving Prisca and Aquila, and a tense question in Genesis 2:19.
Professor Joel Arnold discussed formal-equivalence approaches and the public GitHub documentation, and considered how Hebrew students might examine the translation choices themselves.
Dr. Dirk Jongkind offered time for a focused passage discussion on Greek textual criticism—an opportunity to bring a concrete manuscript question to specialist scrutiny.
Have a passage or source we should investigate? Help shape the next research question through our Open Issues pages and public GitHub discussions. Insight is welcome from every background.
Genesis 3:8 · a question still under review
TWV reads “the man and the woman,” while the Hebrew can support “the man and his wife.” The missing possessive may change the narrative. This is a good example of how feedback can test a well-meant reading.
Explore issue #47 →Beyond one disagreement
The repository also tracks women interpreters, name-order variants, and the English tense of Genesis 2:19, with links to evidence and competing conclusions.
Explore women's interpretation issue → · Names in manuscripts →Bring an observation. Compare interpretations.
Read a passage, investigate where its language comes from, and share what you notice. The community also explores what these ancient texts mean for relationships and shared life today. Religious belief is not required to ask a serious question or contribute a useful source.
Read the edition that suits you
Explore all 66 books, search and bookmark passages, and share a verse with someone who needs it. Keep earlier-language names on the page or switch to familiar English names in the app.
Open the free reader →Discuss meaning and impact
Compare your interpretation with other readers, including people with different religious, cultural and academic backgrounds.
Join the community →Share an observation or source
Point to a word, a manuscript, a translation difference or a real-world implication. Questions, corrections and thoughtful dissent all add value.
Explore insights →Read. Investigate. Discuss.
Test a possible meaning
Compare sources, look at the literary context, and distinguish what is attested from what is inferred.
Share what you notice
Bring a passage, question or interpretation to the community, including its possible implications for life today.
About the text and the research
What is The Way Version?
The Way Version is a complete 66-book English Bible edition shaped by continuing source-language and historical investigation. It includes conventional translation decisions and more interpretive renderings, which readers can examine against the evidence and other editions.
How is it related to The Bible with Original Names?
The Bible with Original Names is the reader-facing edition and app that presents The Way Version. Earlier-language names such as Yeshua and Maryam appear by default. You can choose familiar forms such as Jesus and Mary in the reader and continue reading the same translation.
What does “original meaning” mean?
It means exploring what a passage likely conveyed in its earliest historical and linguistic setting. The work brings manuscripts, language scholarship, cultural context and differing interpretations into view. Each comparison gives readers a richer sense of the words and a way to follow the evidence for themselves.
Why is Aramaic important to this story?
Aramaic was widely spoken in Yeshua’s first-century world, while Hebrew shaped Scripture and worship and the Gospels reached readers in Greek. Reading across this multilingual setting and the Syriac tradition can illuminate familiar sayings, poetic associations and cultural nuances. The Aramaic guide introduces examples and the sources behind them.
How is the translation developed?
TWV began with the public-domain World English Bible and has been substantially revised through ongoing editorial work. We compare relevant Hebrew and Greek textual evidence, language scholarship, context and historical translations. Notes, changes and open questions are available in the public research repository.
Who contributes to the ongoing research?
Readers, contributors and scholars affiliated with Wheaton College, the University of Richmond, Wycliffe College at the University of Toronto, Foundation Baptist College and Tyndale House in Cambridge have brought questions and perspectives to the project. You can help, too: share an insight or suggest a passage for closer study.
How is AI used?
AI tools assist with finding comparisons, organizing research and checking consistency. Human editors evaluate the suggestions using textual evidence, context and scholarship before changes enter the released text.
Can I quote or share a passage?
Yes, the free reader includes shareable verse links. The translation is copyrighted by The Way Partners LLC. Please see the quotation policy and licensing information for uses beyond ordinary sharing.
Read the text. Explore the sources. Form your own view.
The complete translation is available free, alongside articles, language guides, and publicly documented research questions.