integrate tyndale original language texts into core

[chriswep]

original greek and hebrew text from STEPData including variant, morphology, lemma, strong should be added to the core of bibleEngine.

• define a schema for the data
• write a parser for the NT-data
• write a parser for the OT-data
• define output types for the data
• write methods to retrieve the data

[chriswep]

@DavidIB looking at https://raw.githubusercontent.com/tyndale/STEPBible-Data/master/TANTT%20-%20Tyndale%20Amalgamated%20NT%20Tagged%20texts.txt one thing confused me at first: the 2nd column ("editions") in which text-variant the content (3rd and 4th column) appears. However there is an additional "variant" column - i assume the reason for this is to group variants together?

I'm coming from the use case "display the greek text in the H form (Tyndale)" - my first thinking was to take all the rows where "H" appears in the "editions". This is "Database-think" of course. And it shouldn't be an issue to re-group the data while parsing it.

What still confuses me though is that there doesn't seem to be a "base type" that always appears in "editions". To put it another way: what determines which type appears in "editions" and which in "variants"?

So is the understanding of the data correct like this: When we display a "critical text" of the type X, we should go through each row, look where the type appears and display other types (either in editions when X is a variant, or else in variants) as variants. If X doesn't appear at all in the row, display an omission.

[DavidIB]

What you want to do is much easier with a different version of the data which I can't put up publically for copyright reasons.

[chriswep]

What you want to do is much easier with a different version of the data which I can't put up publically for copyright reasons.

if i'd use that data could we include the result in BibleEngine / a public app? If no, it may be better to use what is free?

[DavidIB]

You can use MOST of the data, but it includes some data which is copyright