<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1) Will a StrongsAB lexicon that we can distribute be forthcoming? If not, my intuition is to convert these lemma entries into plain Strong's entries so that they can be useful to those with a Strong's keyed lexicon. At a minimum, I think they should be mirrored as Strong's entries, e.g.:<br>
<w src="4" lemma="strongab:G1510.7.3 strong:G1510">ην</w><br>
rather than:<br>
<w src="4" lemma="strongab:G1510.7.3">ην</w><br>
Thus, the information would all be retained, but the basic Strong's entries would be usable (without some odd changes to the Sword engine).</blockquote><div>Many of the inserted numbers do not have entries in standard Strong's
remotely close in meaning so it would be wrong to do this to all
numbers.<br><br></div><div>A complete Lexicon for the Apostolic Bible will soon be available. I have not yet had time to write a program to generate TEI markup from the tex file it is currently in. We will be charging for the lexicon however so it will be a locked module.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
2) Does it sound acceptable to superscript the prepended numerals in the English, so that they don't disrupt the flow of reading, as it were. (This matches the printed edition.)<br>
</blockquote><div>I hadn't thought of this for some reason but will try to implement this. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
3) Does the markup <seg><hi type="italic">...</hi></seg> universally indicate added text? If so, this can be encoded <transChange type="added">...</transChange>.<br>
</blockquote><div>Yes, italics indicate added text. I will change this. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
4) Can you recommend what to do with strongab:G*, the universally used StrongAB entry for proper names.<br>
</blockquote><div>I could remove all occurrences of G* if you prefer. The best thing to do would be to automatically insert Strong's numbers for available names. However there are many names in the Old Testament that do not have a number. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
(Some other notes on improved OSIS encoding:)<br>
<br>
5) The translated tetragrammaton, currently encoded as:<br>
<seg><hi type="small-caps">lord</hi></seg><br>
should be encoded:<br>
<divineName>Lord</divineName><br>
</blockquote><div>I will change this. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
6) There are lots of extra spaces before punctuation and before each </verse> tag.<br>
</blockquote><div>This can hopefully be corrected with some improvements to my program.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
7) Since there's no Packard morphology content, the osisWork referencing it isn't necessary.<br>
</blockquote><div>Ok. <br></div><br>Daniel<br></div>