Roughed Out Sequence of Applying Final Codings in an OG/LXX Book File (This is just a dump, that I’ll prettify as the manual grows)

Sequence

1) Rubrificate , by the numbers, first <font color=”red”> before the number, then search on “red” and add </font>

at end, or search on 0 through 9 (individual searches) and add </font>

2) Check whether the </> endings only complete the <it>s and <lt>s. If not, note the verse numbers where they appear, and the initial, bracketing element that they complete. If those elements are good code, do searches on telements and then close the element properly, as in <font> . . . </font>.

3) change </> to </i> change <it> to <i> change <lt> to <i>

check your work - See 2) above. I don’t know of other </> endings at this point, but there may be some, particularly with texts that have been color-coded.

4) Then do the C’` changes, L, A, etc. by search and replace on ' ` , including bolding the tags, then italicize those that need it. Be *very* careful here; Composer tends to overdo, changing both c and C to italics, for example.

5) Do the lI and lIIs, by FIRST searching on lII, changing to italics, and THEN searching on lI and changing to italics.

6) Then do standard superscripting, like (mg), La(w) La(s), and such

7) Then look for special cases–and check back with Ziegler, or Wevers, or Rahlfs, or Cambridge ed. – on whether the coded indication is actually correct. That is, if (mg) or {mg} indicate superscripting, are they also used to indicate something else - as in mine, where the (W) for example is not superscripted.

If still sane, go on to the next. :-|

 
for_clean-up_coders_editors_-_the_sequence.txt · Last modified: 2007/08/15 15:58 by petersig
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki