A couple of things to notice:
Variants (the old "O" notes) are now underlined (think: the underlying text)
Different meanings (the old "N" notes) are now shaded (think: shades of meaning)
(though emails can't reproduce shading, so I'm using Grey font instead in the examples below)
This means we can now mix a different meaning and a variant, eg
Ps.2.12: the Son<or: purity |poss: his feet ("and rejoice" moved, based on conjecture)>
Try to use only the following set of reasons for different meanings:
- lit: A more literal translation that reflects the language of the original (not often needed in the ESV).
- ie: A more idiomatic translation or paraphrase in modern English.
- or: An alternative meaning or nuance of the word or phrase.
- old Eng: An archaic translation (usually. reflecting the King James Version)
- sounds like: meaning of a name or a pun in the original (mainly in Hebrew), or where a word might be a name, eg man<sounds like: Adam>
- ie: A more idiomatic translation or paraphrase in modern English.
Put notes IMMEDIATELY after the word, otherwise we introduce new spaces, eg:
Ps.2.1: Why do the nations rage and the peoples plot in vain<or: think foolishly>?
When you use "|" to indicate a new item on a new line, don't leave a space after it, unless you want a space at the start of the new line), eg:
Gen.26.33 Beersheba<ie: 'Well of the Seven' |or ie: 'Well of the Oath'>
Prefix "prob" and "poss" before variants, according to the decisions of UBS
as in the Teamwork document, ie
- Use prob: in NT when option agrees with UBS, and in OT when option agrees with UBS A or B grade, and poss: for others (incl. NT [[UBS]] and OT C & D grades).
Don't bother to collect exhaustive data on variants at this stage - we can do it more quickly in large sweeps later - leave empty brackets if nec, eg:
Ps.4.4 ponder <poss: be bitter (two letters transposed based on ???)>
You can add comments by "Insert" > "Comment"
Hope this isn't too much at once.
David IB
No comments:
Post a Comment