Monday, February 16, 2015

Introduction

Introduction

This blog is not just aimed at pointing out outright mistakes while translating texts from Japanese to English using Google Translate, but to understand and appreciate the process of learning a new language. It is also to emphasize on the fact that language is not just about syntax and vocabulary, but also about the feeling expressed as a cultural entity.

Why Japanese?
I started learning Japanese in late 2014. I work in a Japanese company and Japansese is very essential, not just in the work environment but also in the daily life. Now I'm in my intermediate level of Japanese competency. The communication skills are more about practising with native speakers than simply reading books. That's when you realize that there is a lot of things that is wrong about Google Translate. Yes, it is good and handy when it comes to translating terms, but it often fails when translating sentences. The nuance is lost many a times.

What's wrong with Google Translate?
Google translate uses a word by word literal translation. It sometimes updates its vocabulary with phrases or idioms, but it is a long way from aptly translating a given sentence. I would go to the extend of saying that it lacks the knowledge of grammar and it lacks the flexibility in sentence structure. Especially with a language so intense and complicated as Japanese, one cannot always rely on Google Translate. In fact, it can lead you to awkward situations, as in what you intended to say was completely different from what the Google Translate told you! When I understand the meaning of certain words or phrases; and I try to use Google Translate, this often happens. I have noted a few exceptionally funny ones and will post it soon. As I keep encountering more of them, I would include them as well.

Target Audience?
People with any interest towards Japan or Japanese can find this blog to be interesting. I guarentee you that! You needn't be an expert in Japanese. Just read it with an open mind. That's all I ask for.

Thanks,
Arithy.
2015.02.16.

No comments:

Post a Comment