Might not be an accurate translation but it still speaks the truth. Unfortunately there aren’t many ways of avoiding the future.
Current translation:
OP’s version is more poetic
I agree. Translation is much better these days and I am sure someone else was going to be curious about what the actual translation was.
Good they fixed it but I wouldn’t be surprised if it broke again. Once I was doing a coding project that involved Google Translate and I was using the same sentences for testing. In a week translation has changed 3 times, from bad to good to bad.
Out of curiosity, did it change back to the previous bad translation, or create a new bad translation?
New bad.
It has gotten better since the days of me posting various “Engrish” I would see that were posted officially on wayfinding signage in places like Tokyo and Shinjuku stations, Haneda Airport, rest areas along the national expressway system and so forth.
When I finally go to Japan I’ll be on the quest to collect as many “Engrish” signs as possible! I’m sure some are left!
@hypertown
It’s gotten better but only because the translation algorithms are better. But the rabbit hole gets deep real quick too.
Google Translate is generally hot garbage. I’ve actually found DeepL surprisingly good especially with more “niche” languages like Finnish, although it does definitely sometimes get things hilariously wrong
It seems like the sign is trying to kill me in this translation.
Is that DeepL’s app? I’ve never used it so I have no idea what the UI looks like and I didn’t try to translate the sign’s text with the web version.
Edit: out of curiosity I tried out how the web version handles this sign:
Yeah, it’s the android version.
To be fair, It looks like a problem with the OCR from the app rather than the translation. When I use the phone’s native OCR and copy/paste the text into DeepL Translate, I get the same result as you.
Ah right, that definitely makes sense. I can imagine OCR’ing Kanji could be a bit of a nightmare
