Auto Translate Using King James English?
Comments
-
Check that text in a secular translator like Google or MS translate, it's translating what it really says; it's not specific to a Bible translation.
0 -
I thought they said auto-translate wasn't available for greek, has that changed?
0 -
Don Awalt said:
Check that text in a secular translator like Google or MS translate, it's translating what it really says; it's not specific to a Bible translation.
The thrust of my question was to ask why the auto translator is rendering the English translation in an antiquated form of English...
0 -
Matt Doebler said:
The thrust of my question was to ask why the auto translator is rendering the English translation in an antiquated form of English...
I noticed it does the same thing when you translate the Luther Bibel into English, it uses thees and thous. Maybe it sees a language in an archaic form and translates it into the equivalent English archaic form. Faithlife doesn't control that, it's whatever DeepL or Google Translate have programmed the machine translation to produce.
0 -
Kiyah appears to be correct, that DeepL is choosing to translate that into archaic English. You can see this demonstrated by going directly to DeepL's website and giving it text from Lutherbible 1545 and comparing it to text from Elberfelder 1985.
It is unintended that a translation is provided for the Greek text. We have found that the translation providers do not do a high enough quality job in translating ancient Greek text as if it were modern Greek. We have a case open make sure that this text does not get translated.
Andrew Batishko | Logos software developer
0 -
Andrew Batishko said:
We have a case open make sure that this text does not get translated.
Do I understand this to mean that we won't have auto translate at all for Greek texts? Because I would rather have an archaic-sounding translation than no translation at all.
0 -
Matt Doebler said:
Do I understand this to mean that we won't have auto translate at all for Greek texts? Because I would rather have an archaic-sounding translation than no translation at all.
When we did some testing with allowing ancient Greek to be translated as if the results were modern Greek, the results were very poor (not a matter of having archaic English in the result), but that testing took place some time back. We plan on rechecking the current state of things with DeepL's translation and evaluating whether it is worth enabling in all resources, or if we need to fix the bug that is allowing it to translate text in some resources.
Andrew Batishko | Logos software developer
0 -
Andrew Batishko said:
We plan on rechecking the current state of things with DeepL's translation and evaluating whether it is worth enabling in all resources
Please when you go over this, reconsider the unfortunate decision to not have PBs translated. Thanks!
Have joy in the Lord!
0 -
Andrew Batishko said:
Kiyah appears to be correct, that DeepL is choosing to translate that into archaic English. You can see this demonstrated by going directly to DeepL's website and giving it text from Lutherbible 1545 and comparing it to text from Elberfelder 1985.
I wonder if part of the reason for DeepL and Google doing this is the fact that they train their systems using bilingual websites.
0 -
NB.Mick said:
reconsider the unfortunate decision to not have PBs translated.
Betcha the suits told them not to.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0 -
Robert M. Warren said:
Betcha the suits told them not to.
Suits talk?! I would suspect the issue is one of language coding and variant diacriticals ...
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 -
MJ. Smith said:
I would suspect the issue is one of language coding and variant diacriticals ...
I hadn't thought about that aspect. Since Google has a detection routine, I assume the other service does also. (That could be the reason why incidental languages, like Latin, have to be handled as a separate text selection.) I was assuming legal issues with sending copyrighted material with potentially spooky origins over the internet and receiving it back. Of course, there wouldn't be speculation if we were just given the reasons for non-support at launch.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0 -
Bernhard said:
I wonder if part of the reason for DeepL and Google doing this is the fact that they train their systems using bilingual websites.
Yes, it seems like there's some sort of 'translation by frequently used or traditional block' going on. For example, if John 3:16 in Reina-Valera 1960:
"Juan 3:16 (RVR60)
16Porque de tal manera amó Dios al mundo, que ha dado a su Hijo unigénito, para que todo aquel que en él cree, no se pierda, mas tenga vida eterna."
is auto-translated, it looks like this:
"For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life."
which looks like Geneva / KJV. I am told that the RVR60 provides translation choices from Greek that would look more like the CSB rendering, in that it avoids 'so' and 'whosoever believes', which are sometimes loaded-up with traditional meanings.
"John 3:16 (CSB)
16For God loved the world in this way: He gave his one and only Son, so that everyone who believes in him will not perish but have eternal life."
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
0
