barrucadu / bible Goto Github PK

4fe17cc makes start-of-chapter headings more like body text, in that they get set on the same line as the chapter number and are indented.

This was at the cost of the ragged-rightness. Start-of-chapter headings are now broken over lines by inserting \newline as appropriate, which isn't great. \raggedright works if the heading ends with a \par, but that introduces additional vspace, which is ugly.

Middle-of-chapter headings are fine because they are still proper headings.

Sometimes \columnbreak is needed (eg to prevent a heading from being in a different column to the following verse).

I suspect in just about all cases where I've used \columnbreak by itself, things would look better if:

• Left columns used \vfill\columnbreak
• Right columns used \flushcolsend\columnbreak

Sometimes, at the start of a line, there's excess spacing before the verse number.

I've not figured out the pattern for this yet (if there is one), it could be an issue with the way I've defined the verse spacing.

These headings aren't great because it means that there are two headings in a row (book title and section heading) with no intervening content. Even though the section heading conveys some information, it feels redundant.

There's also a problem of the tops of the columns being unaligned, unless the second column also starts with a heading. That can happen on other pages too, but the first page of a book should look particularly nice.

Alternative solutions could be:

• to raise the column 1 heading (or lower the column 2 start) to avoid the off-balance look
• to set start-of-chapter headings in the same line as the chapter number (rather than the previous line)

The King James Bible distinguishes words which are translator-supplied (i.e. which did not appear in the original Hebrew, Aramaic, or Greek).

In the 1769 version, italics are used:

Deuteronomy

Chapter 1

1. These be the words which Moses spake unto all Israel on this side Jordan in the wilderness, in the plain over against the Red sea, between Paran, and Tophel, and Laban, and Hazeroth, and Dizahab.
2. (There are eleven days' journey from Horeb by the way of mount Seir unto Kadeshbarnea.)

So we should do something like this:

\newcommand*{\supplied}[1]{\textit{#1}}

\verseWithHeading{The command to leave Horeb} These \supplied{be} the words which Moses spake unto all Israel on this side Jordan in the wilderness, in the plain over against the Red \supplied{sea}, between Paran, and Tophel, and Laban, and Hazeroth, and Dizahab.
\verse (\supplied{There are} eleven days' \supplied{journey} from Horeb by the way of mount Seir unto Kadeshbarnea.)

Note that in the 1611 version, Roman type is used instead of Black Letter type:

Like #10.

I'm using "Sabbath" in headings (copied from the NIV) but I think the body text is mostly using "sabbath". As "The Sabbath" is a proper noun I should capitalise it in the body text for consistency with the titles.

The header should say "Deuteronomy 33:17", as that's the first verse on the page. Instead it says "Deuteronomy 34:5", which isn't the first verse or even the last verse, it's part way down the second column.

This only seems to happen on pages which call \flushcolsend so it's probably related to that.

It's not very aesthetically pleasing to have a new chapter start at the bottom of a column, but how little text is too little to allow?

A \columnbreak must be used if there's only one or two lines, as the chapter number is three lines tall and it really looks bad if it dips into the footer. Four lines looks good. But what about three lines? Should that be broken? At the moment I'm doing this inconsistently.

Obviously the text is public domain by now (Fortunately Mickey Mouse was not around in the 16th century), but I'm just wondering about the licensing of the source for your typesetting i.e. main.tex, which I am presuming is subject to copyright, though I have yet to hear of anyone duking it out in court over a latex file, but I think that's more because they tend to be already proprietary and confidential or simply go unpublished.

Reason I ask is I have this late night project over here the Computing Bible, in the vein of the KJB; it's a nice job you've done there and I wouldn't want to just rip it off for legal and moral reasons so I'm wondering what terms you are licensing that under as, well, if you're the author you own the copyright on it whether you want it or not according to at least the US courts, and unless specified otherwise all rights are presumed to be reserved! I'd probably just add a LICENSE file or a comment at the top to make things clear.

The NIV doesn't render the Bible as a solid block of text, eg the song of Moses in Deuteronomy is split over multiple lines and has indented bits.

So, flick through the NIV and see where it breaks the "solid block of text" model and make judgement calls.

• 1 Esdras
• 2 Esdras
• Tobit
• Judith
• Additions to Esther
• Wisdom of Solomon
• Ecclesiasticus
• Baruch
• Letter of Jeremiah
• Prayer of Azariah
• Susanna
• Bel and the Dragon
• Prayer of Manasseh
• 1 Maccabees
• 2 Maccabees

I'm using "Passover" in headings (copied from the NIV) but I think the body text is mostly using "passover". As "The Passover" is a proper noun I should capitalise it in the body text for consistency with the titles.

• Genesis
• Exodus
• Leviticus
• Numbers
• Deuteronomy
• Joshua
• Judges
• Ruth
• 1 Samuel
• 2 Samuel
• 1 Kings
• 2 Kings
• 1 Chronicles
• 2 Chronicles
• Ezra
• Nehemiah
• Esther
• Job
• Psalms
• Proverbs
• Ecclesiastes
• Song of Solomon
• Isiah
• Jeremiah
• Lamentations
• Ezekial
• Daniel
• Hosea
• Joel
• Amos
• Obadiah
• Jonah
• Micah
• Nahum
• Habakkuk
• Zephaniah
• Haggai
• Zechariah
• Malachi

I've already done that for LORD and LORD'S, but there are other instances.

The chapter number should occupy a square box. Instead, the text to its right is ragged, ugly!

• Matthew
• Mark
• Luke
• John
• Acts
• Romans
• 1 Corinthians
• 2 Corinthians
• Galatians
• Ephesians
• Philippians
• Colossians
• 1 Thessalonians
• 2 Thessalonians
• 1 Timothy
• 2 Timothy
• Titus
• Philemon
• Hebrews
• James
• 1 Peter
• 2 Peter
• 1 John
• 2 John
• 3 John
• Jude
• Revelation

Currently I'm doing this manually, but it would be nice to do it automatically.

There's a bit of complication to figure out first: how do I get the fonts inside the container? I could scp them from the host on every build, which is probably the simplest thing to do...

If a section (or, presumably, a subsection) heading is on the line following a chapter number, they overlap.

There is growing awareness of the value of knowing the true name of God (who is commonly translated from the Hebrew, as "Jehovah", Yehovah", "Yahweh", etc).

To maintain the conventions of the pious (those showing reverence for The Name), the KJV translation (and others that followed its traditions), have spelled it as "the LORD".

Issue #11 relates to the function that transforms the text to smallcaps, in keeping with the conventions - but the definite article has been left outside the scope of the function.

If a publisher in future should wish to honour the name of The Holy One, he would need to alter all instances of the text to remove the definite article. It is better to adjust habits without further adue, to prevent retrospective work at that time.

With the present code, we could easily transform every instance to "the Jehovah" by changing the title "LORD" to a name,.. and though it can be technically correct, and it would stimulate a reader's mind, the grammar is simply not good form.

English provides that personal pronouns naturally imply the definite article by virtue of being a name. "Lord" is a title, therefore the definite article is attached to it to transform the title into a name by inference - whereby a reader is led to acknowledge, inevitably, that the lord it names is the sovereign one (ie: "The Lord of lords").

Investigations should also reveal that the context of the references to the name may require exclusions or conditions in the processing to provide for proper figures of speech. Eg: Genesis 24:12, "O LORD" cannot be rendered as "O the LORD" (because he is calling Him by name).