The reason why it still exists is to create an educational hierarchy: the more kanjis you know, the more educated you are. That's polemical and I would not tell it that upfront to my Japanese friends but I feel like kanjis are a vastly inferior writing system compared to the alphabets they have. I stopped caring about kanjis wen I realized that a 15 year old, top of her class, was having difficulties reading news articles because of some words she did not know. To learn Japanese you need to learn to speak it first. Well, that's not possible unless you know about 1000 kanjis, unless you stick with kids book or some mangas (which, actually, I am not that interested in) I live in Japan, tried to learn Japanese like I did learn English and German: through reading, as the true asocial geek I am. If you feel so inclined, mopreme, read my post down below which covers your original blog post extensively and throughout. It seems Google translate cannot read the first Kanji right. To understand why, you need to read my post down the page. But since it's a Chinese word you can used the two sounds ぎょう and ざ in Hiragana to write the two corresponding Kanji 餃子. Get the point? You need Furigana.Ībout gyoza, that's the name of a very popular kind of Chinese dumpling made in Japan, and there is no Kanji for it its written in Katakana only as チャオズ. and so is Rika, Akirako, Yoshiko, Urarako. That's the demonstration that Google Translate has no brain.īy the way Reiko is written 麗子 as a Proper name. But on the right it's messing it right up.
Tagaini jisho sciripting windows#
On Google Translate left windows in the left-bottom corner there is one of the possible correct reading of 淳子殿, namely Junko-dono. For instance 様 or さま is used when referring to customers or clients, but in a business letter you would use 殿 or どの with similar significance. Also for such words there isn't a clear-cut translation, because they are employed as a result of the implications they come with. If the Kanji is adopted looks like 様 reads さま, 殿 reads どの etc. It can be written in Hiragana, like I just did or by using Kanji.
Every suffix has a different and unequivocal use case.
In regular writing to mark Proper names a number of suffix are employed さま, どの, さん, くん, ちゃん and more. Once more Google translate doesn't give a damn if the person using it doesn't know what is doing.
Tagaini jisho sciripting movie#
They made at least one horror Japanese movie out of that story and even Hollywood had a go at it! Now, how many girls you think they have been named Sadako in Japan by their parents? Sadako is Proper name of a popular iconic character in Japanese culture that embodies a little girl killer ghost and it is based on a real Japanese person that was said to be a psychic and lived in the 1900s. 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.
Tagaini jisho sciripting android#
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 kommentar(er)
