Funny thing, I recently found out instagram’s and facebook’s automatic translation feature to be unexpectedly sexist Whenever I write post in Japanese saying that I cooked something, the automatic translation into Polish (which supposedly goes through English on the way) defaults to female forms even though I am male It happens especially if I use 丁寧語.
What is that stupid machine even thinking? That men cannot cook? Duh!
Yes, it is delicious But ,at least when I’m boasting about it on the net, I’m cooking simple Japanese food. Like oyakodon, chicken nanban or okonomiyaki
That’s another drawback with machine translations, and overly cautious humans alike - we won’t call out likely transcription errors we aren’t sure about.
I was confused by the もた but wasn’t sure exactly what it was supposed to have been and it didn’t seem to impact the point I was trying to make too much, so like DeepL I ignored it when I shouldn’t have. That might be a point for google translate’s just giving up approach after all, since it may have been a sign something was off in that area. DeepL will forge ahead taking the input as gospel and producing just as slick English no matter what, and it doesn’t take a lot of kana off to subtly mix things up…
Anyway, sounds like this kind of thing has happened to the character before.
In Google Translate’s defense from JP>EN, if the Japanese is textbook Japanese and doesn’t omit subjects and pronouns, and if the conjugations are not too complex, it’s not bad. Google’s AI doesn’t read context very well, and flails hilariously with complex conjugations and abstract concepts. If you are transcribing conversations and more natural Japanese, especially conversations that describe feelings, analogies, desires and dislikes, Google Translate breaks with humorous results.
You can also improve Google, I assume the same for DeepL, by breaking up and simplifying your text a bit. That assumes that you understand quite a bit of it already though, to allow you to competently disentangle the Japanese!
I think I’ll attach my latest Google Translate fails here too. No complex sentences, no abstract contexts or dialect or anything. It’s just really bad. Deepl fails hilariously too once in a while, but there’s really no comparison.
Sometimes DeepL remembers what you typed before, and sort of… folds that “context” into the meaning of a partial sentence. If you want a fresh translation, you need to clear the box and start over.
This was from a cleared box, haha. I just tried it again just now with the same text in a fresh window, and, yep, same exact translation. For some reason, it translates it better without the period, maybe because it’s trying to force the fragment into a full sentence? But sometimes you get better results with a period
I’ve noticed that too, DeepL really doesn’t do well with punctuation. Sometimes when I copy text to paste into DeepL I accidentally include the period at the end of the preceding sentence (so the pasted text starts with a period). This often results in DeepL adding all sorts of imaginative extra things that are nowhere to be found in the text.
I’ve also seen the translation change dramatically (usually to a more correct one) when I remove commas. Doesn’t it know that commas in Japanese are best ignored unless you’re reading out loud?
That’s one of the few strengths of Google Translate (the only one, probably): punctuation isn’t taken into account at all. Actually, almost anything that might confuse it (further) just gets ignored.
Here’s what happens when you move the period from the end of your text to the start :
Google translate has a finger draw option which I like because then I can write in kanji quickly if I can’t hear the pronunciation to look it up properly.