On Pre-Pub Reverse Interlinear Apocrypha

this is unique...it's not the text itself? Just the interlinear alignment?

I'm not quite sure what's involved in this one...I've never seen anything like it in Logos...

Its a reverse interlinear. With all reverse interlinears already in Logos base packages, you receive the license for the English translation and the original text in the package and then based on the licensing, you then also receive the linked data between the two texts. This is how the ESV RI works, the NASB RI, NIV, NLT, all of them.

This is simply the first time Logos has ever offered one separate of the base package. In fact, the requirement of having licenses to the texts of the reverse interlinears is the main reason why they have up to this point only been available in base packages. But we didn't know what kind of interest there would be in a reverse interlinear apocrypha, so we decided to pre-pub it.

As to whether is will actually show up as a stand alone resource or 'integrate' into our already existent NRSV bible, the prepub page gives the impression it is standalone which I think is a shame. As the following picture suggests the NRSV is begging to have this information added rather than it being in a separate resource.   But as a separate resource I guess it is better than what we have at the moment which is also reflected by this picture.

Andrew, if you could point me to where the pre-pub page suggests such a thing, I'd like to correct that when I get back to the office tomorrow morning. That was definitely not the intention. This will not be a stand-alone resource. It will fill the gap that you see in the picture you provided.

I had tried to avoid implying the possibility that it was a separate resource with the indented statement:

Restrictions and Resource Requirements:
The English-Greek Reverse Interlinear of the NRSV Apocryphal Texts
will only the available for Logos 4 and higher. It cannot be used in
Libronix 3.0 or earlier. Also, it only includes the linked data for the
Greek and English texts. For this reason, both the New Revised Standard Version and the Septuagint with Logos Morphology are prerequisite resources for its use.

Let me know what suggested it was separate and I'll fix it.

That's not the only thing missing:

Actually, MJ, if I may simply repeat you...that is the only thing missing. Fill in the reverse interlinear data and you get the right click information too. The reverse interlinear will fill it all in.

Basically, if you want these holes filled, help Logos get this pre-pub into development!

Are Louw-Nida numbers to be included when you state "They open up a number of avenues of research such as determining whether the translator's rendering of conjunctions, adverbs, and other function words match the semantic range delineated in Louw and Nida's Greek-English Lexicon of the New Testament based on Semantic Domains"?

To be honest, I was thinking more generally about normal lexical searches when I wrote that, but at the same time, I'm 99% sure that the answer is "Yes." L&N numbers will be included.

Thanks for the response Mike,  its not so much what it says, but what it doesn't state that makes you wonder whether this is a stand-alone resource. Maybe a statement along the lines of The data  will be integrate directly into your existing NRSV resource.  If you don't have a license for the NRSV then you will need purchase one and include a link to the NSRV page.  A similar statement about why the Septuigant with Logos Morphology is required and a link to the page to unlock would also be good.

Thanks for the input Andrew. Its always difficult to anticipate what is and what is not ambiguous when we're writing up descriptions. You guys are always a lot of help with that! I've added an additional couple sentences. 

And feel free to keep this thread on top...it just hit about 1/3 of production costs.

Are Louw-Nida numbers to be included when you state "They open up a number of avenues of research such as determining whether the translator's rendering of conjunctions, adverbs, and other function words match the semantic range delineated in Louw and Nida's Greek-English Lexicon of the New Testament based on Semantic Domains"?

To be honest, I was thinking more generally about normal lexical searches when I wrote that, but at the same time, I'm 99% sure that the answer is "Yes." L&N numbers will be included.

I just got word that there isn't any realistic way to include L&N data for the Apocrypha simply because the L&N is specifically limited to the vocabulary of the New Testament. Sadly, the manner in which the lexicon is designed prevents it from being expanded beyond the New Testament.

I assure you I clicked on the pre-order button before even reading the details. However, when I said something else was missing I meant the Biblical Persons information. I am confident it will come but that doesn't keep me from being a bit impatient.

Gotcha.

I was never too worried about whether you would put in an order or not

The update on the page I think now covers it Mike. Thanks for listening to our thoughts.

Of course. You help me do my job better. Thanks.

Could Logos offer a community effort similar to what was done for the original ESV reverse interlinear with the scholar just playing final editor? I'm sure you would get as many volunteers now as then. You could also probably offer less incentive and get a sufficient response

I don't remember that being the case for the ESV...

In any case, the larger portion of the cost involves processing, not production.

However, under Benefits of the RI text there are two mentions of "new testament" that need to be fixed!

Thanks, I fixed that.

Could you state how the link to the Logos LXX works. I understand that the "underlying" Greek will appear in the NRSV resource as per the Greek for the NT but it seems to work differently to the New Testament Greek.

Its the same as in the NT texts. There is no link to the Logos LXX in the Logos LXX. That resource is simply the text used to create the RI and thus a necessary prerequisite. And since the words in that resource share the same tokens. To the extent that sympathetic highlighting will connect the NRSV to the actual LXX resource, they are in a way still connected.