Might not be an accurate translation but it still speaks the truth. Unfortunately there aren't many ways of avoiding the future.
this post was submitted on 14 Jun 2024
11 points (100.0% liked)
Japanese Language
1654 readers
2 users here now
ようこそJapaneseLanguageへ！ 日本語に興味を持てば、どうぞ登録して勉強しましょう！日本語に関係するどのテーマ、質問でも大歓迎します。 This is a community dedicated to the Japanese language. Feel free to come in and ask questions or post your thoughts and opinions about this beautiful language.
Feel free to check out the web archive of r/LearnJapanese's resources if you're looking for more learning material or tools to aid you in your Japanese language journey!
—————————
Remember that you can add furigana to your posts by writing ~{KANJI|FURIGANA}~ like:
~{漢字|かんじ}~ which comes out as:
{漢字|かんじ}
founded 2 years ago
MODERATORS
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.
This problem stems from この先 being able to mean “ahead from here in space”, or in time which (mis)translated to “the future”. Without proper context (that it is a sign on a road) the translation software had to make a guess, and it guessed wrong.
It may be possible to infer from 前へ行く in the second sentence that it is more likely referring to space than time, but I still think it is possible to construct some similar sentences which even humans might misunderstand.
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