In other words feeding people names to Google only shows only one thing. This happens when you are filling a form, in a contract, in IDs etc. If the Kanji of a person have multiple reading such as 淳子, Atsuko, Kyoko and Junko, that person would use what is called Furigana, the Kana only reading showing the sound of that particular Kanji. In such cases one needs to memorize the reading of the character, which reads that way only when it is used for Proper names. There is no translation for these class of words just as there is none for words like Jason, Tom, Samantha, etc. See, Google translate doesn't care if a person doesn't know that when it comes to Proper names such as the name of a person the Kanji reads in a completely different way than the regular dictionary words. Also there are grammatical and syntactical rules that you cannot get right by an educated guess - "educated guesses" such Google translate. People doesn't seem to understand that they cannot have word-to-word translation when it comes to Japanese vs Latin root languages. The variation and unexpected results for what should be exactly the same thing is very interesting. I expected them all to translate to Junko or Atsuko. 私の名前は淳子です! translated to "My name is gyoza!" 私の名前は淳子です。 translated to "My name is Reiko." 私の名前は淳子です translated to "My name is Miko" IOS Contact - see phoneticGivenName, phoneticFamilyNameĪndroid contact - see PHONETIC_GIVEN_NAME, PHONETIC_FAMILY_NAMEįor fun I tried using Google Translate to translate the kanji name in the post 淳子 in various contexts to see what Google thinks it is: For example, both have a Contact object that contain corresponding phonetic-reading fields for first and last names. It's interesting to reflect on what has improved since I wrote it, and what has not.īoth Android and iOS, for instance, provide mechanisms to get this right, if you know to use them and expose them for those locales (and only those locales). Surprised to see one of my old posts on the front page while browsing Hacker News.
0 Comments
Leave a Reply. |