Brenton LXX w/Apocrypha or NETS?

Logos has said that they gave us the wrong version of Brenton's Septuagint as their file did not have the Apocrypha, and they would be fixing this at some time. But it's been a pretty long time.
I would like to have this or NETS in Logos so we can have a full English translation of the complete LXX to scroll with the Greek texts.
Any status date for correcting Brenton? Any word on NETS for Logos?

Find more posts tagged with

Comments

DMB

For me Brenton is irrelevant since I have Original Languages. That's the package that purports to emphasize 'original languages'.

An english translation of the LXX sounds so esoteric. Pretty much everyone reads greek anyway, so I can't imagine who would need it.

NETS seems above Logos' level. That's why I have Olivetree.

As I understand it, Olivetree will soon offer a Coptic Dictiionary, along with the Samaritan Pentateuch.

David Knoll

Use both and think about the reasoning behind each translation decision. Note that the Vorlage can sometimes be different (NETS use the Goettingen edition as their base text)

Eric Weiss

https://community.logos.com/discussion/comment/266338#Comment_266338

For me Brenton is irrelevant since I have Original Languages. That's the package that purports to emphasize 'original languages'.

An english translation of the LXX sounds so esoteric. Pretty much everyone reads greek anyway, so I can't imagine who would need it.

NETS seems above Logos' level. That's why I have Olivetree.

As I understand it, Olivetree will soon offer a Coptic Dictiionary, along with the Samaritan Pentateuch.

Well, I have Platinum, as well as Göttingen Septuagint, so I have more original Greek than I can shake a stick at. But since I'm not fluent in the language, though I can follow/read/translate it, and reading the glosses in the Lexham Interlinear Septuagint can be a bit tedious, it's nice to have a scrolling/synced English translation when I'm reading, and especially if I do a passage list from a search in the LXX. Some of my blogposts and Facebook posts deal with the LXX text, and since most of my followers and friends can't read Greek, it's nice to have a simple copy-and-paste way to put both the Greek and the English LXX text into a post. Since many LXX morph searches return hits in the Apocrypha, the fact that Brenton's as a version for a passage list returns blanks for those verses makes things more complicated than they need be. Plus, Logos admitted it was their error to load/sell the non-Apocrypha version of Brenton, and it seems to me that we've waited long enough for it.

Brian Davidson

https://community.logos.com/discussion/comment/266338#Comment_266338

[deleted by author]

DMB

https://community.logos.com/discussion/comment/266396#Comment_266396

Brian ... only packages above Original Languages have Brenton (why I've no idea). I've no need to upgrade for an older LXX translation.

And as you may already know, NETS is fairly widespread ... it's just not in Logos. So, it's an interesting question concerning Brenton vs NETS but Logos' odd support for LXX translations is even more interesting.

The statement about everyone reading greek is false on its merits (and should be obvious). But the statement is implied by Logos' limited support for LXX translations. I'm hoping at least the NRSV apocrypha reverse will show up soon.

I have both Olivetree (NETS) and Laridian (Brenton). Thus my additional point concerning the Cadillac of Biblical software.

MJ. Smith

https://community.logos.com/discussion/comment/266397#Comment_266397

Note also that there are two translation projects underway of the LXX for Orthodox use.