- Aug 12, 2017
- 707
- 1,924
A warning to Deepl fans/translators/evangelists since I suspect we'll see a lot if deepl MTL's in the future
When deepl cannot understand/translate a sentence it can and will:
(1) remove the part that could not handle...
(2) return it as untranslated text....
(3) return a strange result like e.g.
(1) is somewhat problematic since it can brake the code. (we'll see a lot of broken games in the future...)
Solution: do not use deepl for translating parts that may contain code.
Translating lines that have symbols like
(2) is a bit problematic but you can identify and fix them when reviewing the translation.
(3) is the hardest to fix.
You believe that Deepl did a great job translating your text but in reality deepl is "messing" with you
since you cannot understand the source language.
phrases/translation responses like:
and probably a hell lot more fake translation/responces that I missed... (I'll update the list if I catch/identify other phrases)
Sollution: Review the entire translation and try to figure/catch those bogus parts.... (or use Google, Bing, Papago, etc. to compare side by side )...
ps1. Probably Deepl devs think that is funny and it is... (until you realize what is happening)...
but I'm surprised that so many people like so much this "better"machine translator.
And this is advertised all over the net as the best machine translator...
ps2. If they ever remove the no.(3) results I'll remove the "" comment...
edit:
ps3. To any fanboy/whatever... that feels the urge to comment...
This post/thread is made to warn developers for deepl's shortcomings and what they should double check when/if they use this service...
Is not a post that compares machine translators...
When deepl cannot understand/translate a sentence it can and will:
(1) remove the part that could not handle...
(2) return it as untranslated text....
(3) return a strange result like e.g.
What?.(1) is somewhat problematic since it can brake the code. (we'll see a lot of broken games in the future...)
Solution: do not use deepl for translating parts that may contain code.
Translating lines that have symbols like
/\[]{}:%#* is a asking for trouble.(2) is a bit problematic but you can identify and fix them when reviewing the translation.
(3) is the hardest to fix.
You believe that Deepl did a great job translating your text but in reality deepl is "messing" with you
since you cannot understand the source language.
phrases/translation responses like:
Code:
I'm not sure what to say.
I'm not sure what to do.
I don't know what to say
I don't know what to do.
I don't know.
I don't think so.
Eh?
What?
No!No!No!
I'll try.
I'll be back.
I'm sorry about the .......
That's it, that's it.
I'm sure you'll be happy to hear that.
I'm sure you'll be happy with the results.
I'm not sure what to do with it.
I'm not sure if I'll be able to do that.
I'm sorry!
I'm sorry!I'm sorry!
I'm sorry!I'm sorry!I'm sorry!
Eh?What?I'm sorry!
I'm not sure if this is a good idea or not.
I can't believe it.
I've never heard of that.
I've never heard of such a thing!
I don't know.
I'm not sure if this is a good idea or not.
I don't know what to do.
I'm not surprised.
I'm not sure.
I'm not sure what to make of it, but I'm sure it's worth it.Sollution: Review the entire translation and try to figure/catch those bogus parts.... (or use Google, Bing, Papago, etc. to compare side by side )...
ps1. Probably Deepl devs think that is funny and it is...
(until you realize what is happening)...but I'm surprised that so many people like so much this "better"machine translator.
And this
is advertised all over the net as the best machine translator...ps2. If they ever remove the no.(3) results I'll remove the "
" comment...edit:
ps3. To any fanboy/whatever... that feels the urge to comment...
This post/thread is made to warn developers for deepl's shortcomings and what they should double check when/if they use this service...
Is not a post that compares machine translators...
Last edited: