16 replies to this topic

[EmethAlethia]

I have been working on a project, for the last 10 years, with a professor, that includes:

• Aall (4) of the major Greek texts for the New Testament
• All of the available Septuagint manuscripts
• All the Hebrew manuscripts
• "Possibly including the dead sea scrolls scripture fragments as well"

The existing files show:

• ALL variations in Greek Words in ALL the N.T. Documents by verse
• ALL available Strongs Number information for all N.T. variants
• ALL the Morphology for all N.T. Variants
• ALL Pronounciation for all N.T. Variants
• A set of new numbers that specify a unique number for Each and every variation of each and every Greek word used in all 4 documents. (Preceded with a "W").
• When a variant is presentm the entire word column shows in red, and the variant document is indicated by the blue letters at the bottom.
• ALL of the above for ONE complete Septuagint version, with the exception that we currently only have English for that version from Genesis through Deuteronomy 5

All underlined text indicate a link to other detailed files as specified above.   Here is a sample from Mat. 2;3


3      W01319 W08635 W20670 W30017 W06832 W20670 W18558 W22864 W32434 W22114 W28519 W06050      G0191 G1161 G2264 G3588 G0935 G2264 G5015 G2532 G3956 G2414 G3326 G0846      VAAPNSM CONJ NNSM TNSM NNSM NNSM VAPI3S CONJ ANSF NNSF PREP PGSM      ακουσας δε ηρωδης ο βασιλευς ηρωδης εταραχθη και πασα ιεροσολυμα μετ αυτου      äkewsäs de ārōdās ο bäsιleews ārōdās etärächthā kī päsä ιerοsοlewmä met owtew      HAVING HEARD BUT HEROD THE KING      HE WAS TROUBLED, AND ALL JERUSALEM WITH HIM.                b s t           a                                      

** Note: Html shows up much nicer in the screen I entered it on than it does when it actually posts to the forum. Things aren't squished together, and show up in their own perspective boxes, in their own columns. I guess I don't understand how to post the code and have it show properly.


     The files are currently in HTML by chaper for the bible, and by individual strong's number, morpholology code, and varaiant indicator character.

   We already have a second "Variant" of the Septuagint, and we are finishing the English, and the variant indications for both of these versions in parallel, but they are still in a raw data format, and haven't been converted to HTML as of yet.

There are (2) other Septuagint variants out there, and we are hunting for the information right now. (If anyone knows where we can get those files, that would be appreciated as well.)

Eventually we want to tie the Greek O.T. words in Hebrew (All major documents, with the Variants, in the same file, or with links to move back and forth between the Greek and Hebrew so people can see the consistencies between ALL Documents, Old and New Testament Greek, and Old Testament Greek and Hebrew, WITH ALL MAJOR DOCUMENTS included. (Any ideas on how to do this would be nice as well.) In the meantime, ...

What I am looking for is:

A step by step instruction manual for how to convert "our" current version of "our" HTML file program into an e-sword module ... and the part that will probably be a nightmare, .... with all links intact.

Does such a set of instructions exist? Is there anyone, with experience, who wants to help?

[jonathon]

Eventually we want to tie the Greek O.T. words in Hebrew (All major documents, with the Variants, in the same file, or with links to move back and forth between the Greek and Hebrew so people can see the consistencies between ALL Documents, Old and New Testament Greek, and Old Testament Greek and Hebrew, WITH ALL MAJOR DOCUMENTS included. (Any ideas on how to do this would be nice as well.) In the meantime,

Recast everything in OSIS format.

Also talk to the guys at the Open Scriptures Project. ( http://openscriptures.org/ )

Does such a set of instructions exist?

From OSIS, yes. From SFM, yes. From USFM, yes. From USFX, yes. From XSEM, yes.

From HTML, no.

jonathon

[Josh Bond]

Recast everything in OSIS format.

Also talk to the guys at the Open Scriptures Project. ( http://openscriptures.org/ )



From OSIS, yes. From SFM, yes. From USFM, yes. From USFX, yes. From XSEM, yes.

From HTML, no.

jonathon

Yeah but he's wanting to get to e-Sword format. I'm not sure how casting the text in OSIS markup would help get it to e-Sword format?

[jonathon]

I'm not sure how casting the text in OSIS markup would help get it to e-Sword format?

OSIS is specifically designed for semantic markup, which is what this project requires. HTML is utterly incapable of indicating, much less preserving, semantic markup.

Furthermore, the tool chain assumes OSIS, not HTML.
(If Hendo1986 wants to convert their interlinear to e-Sword, etc, they will need to recast it in OSIS format.)

jonathon

[Josh Bond]

How do you get from OSIS to e-Sword without losing data and/or hierarchical structure? OSIS is a markup that really doesn't translate to e-Sword's RTF format, mostly because e-Sword isn't a real markup syntax in the structured (hierarchical) sense OSIS is.

I believe OSIS is a great format for his resource. I just don't think there's proper support within e-Sword for this resource, especially the formatting he describes and the links.

[jonathon]

How do you get from OSIS to e-Sword without losing data and/or hierarchical structure?

Inline comments.

jonathon

[dyan]

Hi,

What is the procedure to input Inline comments?

[Josh Bond]

I think he means something like this [and your note goes here] and you continue talking here [and these are a little disruptive] but you can keep adding them [anytime you want to expand your thoughts].

[EmethAlethia]

Thanks for the help so far. The HTML code is something that I generated programatically in Visual Basic from a few different Excel master files loaded into SQL Server. I have the Excel Files, and the SQL files developed from these, available, and if I can figure out a format that will work, and the format I need to get things into, I can generate ANY text file, or other file, with any formating that we might want.

A.) Strong's Number Information (An Expanded Strong's number definition showing ranges of meaning.)
B.) Unique Word Number (Same as Strongs, but only for "THE EXACT SAME GREEK WORD", giving the exact word meaning.)
C.) A Variant Table listing which variants the codes in the master file represent, and where the manuscript came from.
D.) Morphology Table for all the different possibilities of Morphology coding

Gentlemen, since what I already have will not work, can I get an idea of exactly what format I need to get each of these tables into, that will work? I tried to open up an e-sword bible (.bblx) in the latest format in Microsoft access to see what formatting was included in that file, after changing the extension, but I couldn't get it open. I would think that, if I could programatically generate whatever file format that e-sword uses, that should work, and if I could generate a different Strongs Number File, that should be replaceable as well. I have seen files with Morphology information, but I do not believe that was linked to anything, so perhaps that isn't possible. I have never seen anything with variant links or "Unique Word" numbers linked, so maybe that isn't possible as well. But, I am new to trying to make this work.

If nothing else, it would be nice to offer what I can for e-sword. If there is some other programing format that allows all the rest of the capabilities, but will allow me to get this information into the hands of the church, I am open to that as well.

[Josh Bond]

e-Sword bblx files are SQLite databases rather than MS Access databases. You can open and view a bblx module in a SQLite database viewer, as long as the bblx file isn't encrypted. I don't believe you will come close to the functionality you presently have in HTML because e-Sword does not support a linking system.