Any brief sections that are separated from the main flow of a chapter should be tagged as asides using the HTML <aside> element. (Pull quotes are an exception to this rule for our EPUBs. For pull quotes, see the CSS Library)
Use <p epub:type="bridgehead"></p> for any headings in an <aside> section.
<aside> <pepub:type="bridgehead">Greek Highlight</p> <p><spanclass="bold">Blessed. Greek</span><spanclass="lang-grc">μακάριος</span> (<spanclass="translit">makarios</span>). This term occurs ...</p> </aside>
HTML Semantics
As instructed in HTML semantics, always use the most semantically-appropriate HTML tags as you markup content. Lists should be ordered or unordered HTML lists. Outlines should be ordered lists with the appropriate classes. Block quotes and poetry should always be tagged as such, and so on.
Hyperlinks
Our current practice is to add links to URLs. The link must contain:
We prefer using Unicode characters for foreign languages or transliterations, but in some circumstances, character entities are necessary to get things to render properly.
For Greek and Hebrew, the mywsb.css classes .lang-grc and .lang-hbo will set the fonts to Gentium Plus and Ezra SIL, respectively.
Sometimes a combination of Hebrew and non-Hebrew characters has trouble rendering properly because Hebrew reads right-to-left. In these cases, it can be useful to use the dir attribute. Surrounding the entire phrase in an element with dir="ltr" and each series of Hebrew characters with an element having dir="rtl" can help.
Also in mywsb.css, the classes .lang and .translit will both set the font to Gentium Plus italic, and is useful for setting these words apart in the flow of text.
<!-- Other languages --> <span class="lang">exegético</span>
Scripture quotes should be tagged as blockquote elements, and may use the mywsb.css class .scriptext
<blockquoteclass="scriptext"> <p>For those He foreknew He also predestined to be conformed to the image of His Son, so that He would be the firstborn among many brothers. And those He predestined, He also called; and those He called, He also justified; and those He justified, He also glorified. (Rom 8:29–30)</p> </blockquote>
Poetry
For poetry, mywsb.css has a series of poetry classes, (poem1-10 or poetry) giving increasing levels of indentation. Be sure to follow the indentation conventions of the source material. Nested <div class="poetry"> tags create indented blocks.
<!-- Poetry example from the CSB, Genesis 2:23-24 --> <p>And the man said:</p> <divclass="poetry"> <p>This one, at last, is bone of my bone</p> <divclass="poetry"> <p>and flesh of my flesh;</p> </div> <p>this one will be called “woman,”</p> <divclass="poetry"> <p>for she was taken from man.</p> </div> </div> <p>This is why a man leaves his ...</p>
<!-- OR --> <p>And the man said:</p> <pclass="br-before poem1">This one, at last, is bone of my bone</p> <pclass="poem2">and flesh of my flesh;</p> <pclass="poem1">this one will be called “woman,”</p> <pclass="poem2">for she was taken from man.</p> <pclass="br-before poem1">This is why a man leaves his ...</p>
Rendered version of the example code:
If the poetry was written by someone other than the author, it also needs to be wrapped in a blockquote tag.
Chiasm
A chiasm is a literary device that uses a repeating A-B-C … C′-B′-A′ pattern for clarification and/or emphasis.
For a chiastic structure indentations, you may use the poetry classes above.
<pclass="poem1">A "No servant can serve two masters;</p> <pclass="poem2">B for either he will hate the one,</p> <pclass="poem3">C and love the other,</p> <pclass="poem3">C' or else he will hold to one,</p> <pclass="poem2">B' and despise the other.</p> <pclass="poem1">A' You cannot serve God and mammon."</p>
Quotation Marks
Typographic (curly) quotes and straight quotes are equally acceptable in book text. Simply leave the quotes as received from the source.
All tables should have the epub:type="table" applied to the table tag.
<tableepub:type="table"></table>
Style name for the table should be:
table | number of columns | col, example: <table epub:type="table" class="style">
All tables should have an id, this id is what should be included in the toc.xhtmlepub:type="lot". If a table doesn’t have a name applied by the content it should be named: chapter | increment.
If a table style is generic throughout the content then the width on the <td> can be removed and a generic name can be applied. If an table is heavily detailed and larger than 4 columns it can be included as an image but should be referenced in the lot and not the loi.