Giter VIP home page Giter VIP logo

escripture.github.io's Introduction

World English Scripture

Online at escripture.github.io
Chapter and verse numbers can be enabled and disabled by tapping/clicking anywhere on the page when viewing the text.

A revision of the 2023 World English Bible, which is based on the 1901 ASV, which is based on the 1611 KJV, much of which is based on the 1530 Tyndale version, which is based on the Greek 1516 Textus Receptus and the Hebrew 1008 A.D. Masoretic Text.

In the few revisions made, this version tends to favor the Hebrew 1380 Shem Tov manuscript and Syriac manuscripts for Matthew, because of their independence from Roman and Greek influence. Conversely, the Genesis chronology restoration is based primarily on the Greek Septuagint in order to make up for deficiencies in the Hebrew Masoretic Text.

The following is a brief outline to answer the following questions:

  • WHAT has been revised?
  • And WHY has it been revised?

  1. Base book selection on Yahweh and Yahushua.
    Yahweh instructs us to listen to his son, the Messiah, Yahushua (Matthew 17:5). Yahushua is reliably quoted in Matthew. He cites the Law and Prophets (Matthew 5:17-19). He also quotes Psalms, and Yahweh is quoted in Psalm 2. In Ezekiel, Yahweh mentions Job twice, and Yahweh is quoted in the book of Job. Any text presented here must pass the test of Deuteronomy 13. The focus of the collection presented is the sayings of Yahweh and Yahushua.

SPECIFIC EDITS
These edits pertain only to specific verses.

  1. Restore Genesis chronology according to Henry B. Smith Jr.'s 2018 proposal.
    Scribes corrupted the Masoretic Text, but we can restore it.

  2. Translate "בעל" as "owner", not "husband", except for nouns and idioms.
    The adjective "בעל" means owner, or master. "Husband" is a poor translation.

  3. Remove Roman/Greek Trinity and Virgin Birth bias.
    They're Anti-Torah, and bias is not true to the text.

  4. Restore 'do not swear' to 'do not swear falsely'.
    The Shem Tov provides a Torah-compatible rendering.

  5. Omit possible additions to Yahushua's prayer.
    Prefer the Nestle-Aland and United Bible Societies reading over tradition.

  6. Omit unlikely verse Matthew 17:21.
    This verse may have been inserted to support asceticism. Prefer the Syriac manuscripts and Nestle-Aland and United Bible Societies reading.

  7. Omit unlikely verse Matthew 18:11.
    Prefer the Syriac manuscripts and Nestle-Aland and United Bible Societies reading.

  8. Clarify the word "divorce" to "put away" when applicable.
    Prefer a Torah-compatible translation found in The Scriptures 1998 by Institute for Scripture Research, and other translations including the KJV.

  9. Restore "Power" to "Yahweh" in Matthew 26:64.
    It seems more likely than not that Yahushua spoke Yahweh's name, especially given that he says he makes the heavenly father's name known, and in understanding the context of the passage, especially in contrast with the Septuagint translation of Leviticus 24:16. The Scriptures 1998 by ISR restores his name very liberally. Of all places to restore it, this seems most justified. The reaction Yahushua experienced doesn't really make sense unless he spoke Yahweh's name.

BULK EDITS
These edits apply to words and phrases throughout all books.

  1. Restore title "God" to "Elohim".
    Avoid using a questionable word. Transliterate instead.

  2. Restore word "Holy" to "Set-Apart".
    Avoid a questionable word, and improve translation clarity.

  3. Translate "איש" as man, not husband, and "אישה" as woman, not wife.
    Husband/wife are terms foreign to Hebrew and Greek that may add confusion.

  4. Restore name "Jesus" to "Yahushua".
    Restore name to more accurate transliteration.

  5. Restore phrase "became the father of" to "brought forth".
    Avoid the phrase "became the father of", which is poor translation, and has doctrinal issues, and instead use a literal translation.

PRESENTATION
These edits affect the formatting, online or in print.

  1. Omit chapter and verse numbers.
    Except for Psalms, numerical divisions are not scripture, and they obstruct the text.

  2. Omit footnotes.
    Translation notes and cross-references are unnecessary and distracting.

  3. Disable red lettering.
    Red lettering adds biased opinion. It is not a characteristic of the manuscripts.


For detailed information about each translation decision, see the setup.sh and index.html source code.

This version is not a declaration of canon. The books and text presented are those which the developer feels can be presented in good conscience.

This page may move in the future, without prior notice or redirect! For reliable continued usage, you may download the files. Everything here may be copied freely.

This version has been adapted from the "WEB" version by Allen Ereaux, AKA Emmanuel Abraham Eraut. If this page moves, the new address may be posted on one of these accounts:

Feel free to contact the developer at [email protected]. Corrections and concerns are welcome. Alternatively, you may post a public message to the developer through a media account listed above, or submit an issue here on this site (if applicable).

escripture.github.io's People

Contributors

escripture avatar

Watchers

 avatar

escripture.github.io's Issues

Suggestion: use a USFM to HTML converter

If you stay with USFM through the seds and use a USFM to HTML converter you could probably keep/add footnotes easily e.g.
https://github.com/mondele/usfm2html/tree/master
https://github.com/Bible-Translation-Tools/USFM-Converter
https://github.com/WycliffeAssociates/quick_usfm_converter

and it's probably easy to go from USFM to sword/e-sword/OSIS
https://github.com/JohnAustinDev/osis-converters
https://github.com/adyeths/u2o

so that your work could be used by others who use bible reading software.

Break setup.sh into smaller files for the seds

Break setup.sh into smaller files so we can separate USFM fixes and isolate text corrections by Testament and book. Then the sed changes can be used by other people to adopt in their canon, and apply the seds to something other than your WEB text.

Suggestion: make a subdirectory of sed files

Just a suggestion: make a subdirectory of sed files and break setup.sh into a series of sed -f sec/topic.sed so you can group together sed changes by topic, and better document the reasons for the changes. sed ignore '#' comments, and if you need to, you can add a topic.txt file to explain the changes in topic.sed

It would also make it easier to select topics that can be exported to the TSV format so that I could include them in an OSIS commentary file that reads alongside any translation Bible.

Beyond the 2 TSV files I uploaded of URLs linking to https://jesusbible.github.io and links to Doug's youtube videos, I have for example a list of all the translators' footnotes to the KJV.

Suggestion: leave verse numbers in

Just a suggestion: leave the verse numbers in so that it's easier to use with Bible software and commentaries that are keyed to verses.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.