I believe this is an issue....

If I run a bible word study on ὥστε and look at the translation ring in the ESV it is radically different than if I look at it in the NASB.
Let me try to show what I mean.
If you notice in the ESV, all you have is "so". That could be when ὥστε is translated "so", "so that", "so as to", "so then", etc. I don't want to have to look through all those different selections, I would expect it to be able to do what the NASB's translation ring does and show me the "so that" vs. "so then" for example.
Some of the translations have this problem (like ESV here) and some don't (like NASB here). It suprised me to see that LEB also has this problem.
I'm imagining this is an issue with how the interlinear is tagged and I doubt Faithlife wants to undertake a huge reworking of that. But something like this is super annoying for someone trying to look at how ὥστε is translated in their preferred translation (ESV) and it doesn't even show them the proper results.
I'm super thankful for all that Faithlife does. Just wanted to point this issue out if it hadn't been already. Thanks!
Comments
-
Ryan Robinson said:
I'm imagining this is an issue with how the interlinear is tagged and I doubt Faithlife wants to undertake a huge reworking of that.
The tagging is inconsistent. But there could be room for improvement in the BWS when you look at the Translation section of the Information tool --> it displays "so that" for both ESV and NASB95 in Mt 8:24, 12:22
Dave
===Windows 11 & Android 13
0 -
A very subtle issue - note ESV has two tone blue; NASB has only one tone - and that makes all the difference.
There is also a bad character in the NASB95 - not relevant to your issue:
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0