SansBlogue  
Monday, May 01, 2006
 
Notes for authors: third part: draft please comment ::

Here's the final part, please do leave or send comments...


3. Technical details

Wordprocessors: all text for HBC_ should be prepared in a either Open Office or MS Word (except by special arrangement).

Templates: use the supplied Template, (and not another like the MSWord "normal" template. Please make no changes made to the Styles in the Template. (For more details see the guide for either Open Office 2.0 or Microsoft Word2003.)

Characters from non-Roman alphabets and other special characters should either be standard Unicode, or produced in Times New Roman using the | Insert | Special Character| (Open Office) or | Insert | Symbol | (MS Word) functions (the writing system should be indicated using the “character” Styles “Hebrew” or “Greek” from the supplied Template).

3.1. Styleguide

This is a longer quotation in the Style “Quotation” the words quoted should be followed by a reference in brackets, either a Bible reference in SBL style or to the work cited. E.g. (Am 3:12) or (Blogs, 63)

3.2. Signalling links

Authors should aim to indicate where links are needed or may be created. There are two methods of doing this. The approach outlined here is easier and cheaper to convert, however if you find this inhibits your editing of the text then simply place the indications of links as comments, with the highlighted words forming the link text. (In Open Office only the end of the selected text in highlighted, so the beginning should be indicated by a double asterisk, see sample.odt)

3.2.1. Justification and explanation

Where you create “justification” or “explanation” lexia you should think about how, and from where, these lexia will be accessed. Links are normally made from sections of text (usually just one or a few words long), which themselves suggest or at least hint at the linked material. Such text should be enclosed within double asterisks and include an indication, within square brackets inside the asterisks, of whether the link provides justification (“J”) or explanation (“E”) followed by the filename of the linked lexia, still within the asterisks. Thus if you write:

**this explains linking [E links.doc]**

the text “this explains linking” will be linked via a link marked as an “Explanation” to the file named links.doc.

3.2.2. Internal links and anchors

It may sometimes – most often where a longer lexia needs a list of headings at the start, for example linking to verse level comment within comment on a unit – be necessary to link to a location within a lexia. These may be made using:

3.2.3. University Bible Dictionary articles

Often it will be useful (think particularly of untrained readers) to link to a Bible Dictionary article.

Where such an article exists in the UBD, or where such an article is listed as desirable, if possible make the link text in your lexia the same as the head word (or term) of the dictionary entry mark the term with double asterisks and the mention [UBD] thus “the **kingdom of God [UBD]**” will link to the article headed “kingdom of God” as will "the **kingdom of heaven [UBD kingdom of God]**".

If no such article is yet listed, but where you think one would be desirable add double asterisks round the mention UBD to indicate this to the editor e.g. “**Ugaritic mythology [**UBD**]** is particularly…”

Where either you do not think it likely that the UBD will need to include an article, or you prefer to create your own, make the link as a standard “explanation” (see above).

3.2.4. Bible references

You should take care that Bible references are given in standard (SBL) abbreviated format with the book name included (e.g. Is 5:3). You should mark them as links with asterisks and the mention [Bible reference] thus: “later in the chapter (**v.13 [Bible Is 5:13]**)” will read “later in the chapter (v.13)” where v.13 is a link to Isaiah 5:13. If you need to make reference to a particular translation you should usually quote the text directly.

3.3. Styles and how to use them

As we have seen above, with VERY few exceptions NO styling should be used that is not applied as either a “paragraph” or a “character” Style. So I will include some simple instructions for those not yet very familiar with Styles:

3.4. How NOT to format

3.4.1. Tabs, tables and spaces

3.4.2. Fonts

Do NOT use fonts at all. They should ALWAYS be assigned by the Style chosen.



[1] Patrick H. Alexander, et al. (eds.) The SBL Handbook of Style: For Ancient Near Eastern, Biblical, and Early Christian Studies (Peabody, Mass.: Hendricksen,1999)

[2] If such a style is needed and does not already exist contact the editors and one will be added to the Template.



SEARCH Tim's sites
Posts listed by topic
My academic CV



Write to Tim

archives:
January 2004 / February 2004 / March 2004 / May 2004 / June 2004 / July 2004 / August 2004 / September 2004 / October 2004 / November 2004 / December 2004 / January 2005 / February 2005 / March 2005 / April 2005 / May 2005 / June 2005 / July 2005 / August 2005 / September 2005 / October 2005 / November 2005 / December 2005 / January 2006 / February 2006 / March 2006 / April 2006 / May 2006 / June 2006 / July 2006 / August 2006 / September 2006 / October 2006 / November 2006 / December 2006 / January 2007 / February 2007 / March 2007 / April 2007 / May 2007 / June 2007 / July 2007 / August 2007 / September 2007 / October 2007 / November 2007 / December 2007 / January 2008 / February 2008 / March 2008 / April 2008 / May 2008 / June 2008 / July 2008 / August 2008 / September 2008 / October 2008 / November 2008 / December 2008 / January 2009 / February 2009 / March 2009 / April 2009 / May 2009 / June 2009 / July 2009 / August 2009 / September 2009 / October 2009 / November 2009 /

biblical studies blogs:

other theology/church blogs:

x


Powered by Blogger


Technorati Profile

Yellow Pages for Auckland, New Zealand