Tagged texts

The deal about tagged texts is this (as I understand it):

Fully tagged OT Hebrew is not available for free
Limited tagging is available as PD for the KJV
- it is limited to partial parsing of all verbs and Strongs numbers on all words.
- I think this is fine, cos the full tagging doesn't add very much that is useful
This limited tagging has been ported to the NASB (aka NASV)
- I think this project was done by a team of Troy's, but it belongs to someone else
- I understand that permission is usually given to anyone who wants to use this for free software
- it was originally prepared for the old 1977 NASB and updated for the 1995 ed (called NAU in BibleWorks)
This tagging MAY be ported to the ESV in the future
- Troy has initiated a project, though I don't know how it has progressed
- Crossway may be doing something similar (even though they also asked Troy to do it)
- the reverse interlinear published by Crossway and Logos could be turned into a tagged text
  (I don't know why they haven't done this, and we could ask permission to do it for them in return for using it)

What I'm planning for the project is this:

We will make our own interlinear from the NASB.
Here's how:
1) Use the PD tagged Hebrew text (Westminster text with the same limited tagging as the NASB)
2) Use the tagged NASB with permission
3) tie the two together by means of the Strongs numbers
4) display them together
   either (a) as interlinear (I don't think we even want to offer reverse intelinear)
   or (b) as parallel texts where each highlights the other as you hover over a word
   (see eg at http://biblewebapp.com/study/#ref=Gen%201:1|ver=he_wlc,en_nasb)


Potential problems:
Using an automatic method like this to produce an interlinear won't produce an approximation of a flowing translation under the text like some clever interlinears do.
I suggest we don't try. The interlinear will simply contain whatever English words are tagged with the same Strongs number as the original.
Because of the incompleteness of the Hebrew tagging, the use of parallel texts (4b above) doesn't work well, because it implies there is no Hebrew behind words which are untagged. The interlinear approach will show translations for all the words except things like 'eth' (the) so it is, effectively, a helping hand to non-hebraists (and hebraists alike).
If we use an interlinear, we will need a full translation alongside - but we would want this anyway. We can offer the ESV by default and then let people choose whatever version (or other versions) they want to see. 
I suggest we don't have a separate line for morphology, because in the OT a lot of this will be missing, and anyway it is largely distracting - so keep the morphology to popups which also have links to lexicons.


David IB