{"id":3077,"date":"2009-12-22T15:38:55","date_gmt":"2009-12-22T07:38:55","guid":{"rendered":"https:\/\/pinyin.info\/news\/?p=3077"},"modified":"2015-11-17T15:06:46","modified_gmt":"2015-11-17T07:06:46","slug":"google-translate-and-romaji","status":"publish","type":"post","link":"https:\/\/pinyin.info\/news\/2009\/google-translate-and-romaji\/","title":{"rendered":"Google Translate and rōmaji"},"content":{"rendered":"

The following is a guest post by Professor J. Marshall Unger<\/a> of the Ohio State University’s Department of East Asian Languages and Literatures.<\/p>\n

The challenge<\/em><\/p>\n

On 18 November 2009, Mark Swofford posted an item on his website pinyin.info criticizing the way Google Translate produces Hanyu Pinyin from standard Chinese text<\/a>. He concluded by saying, \u201cGoogle Translate will also romanize Japanese texts written in kanji and kana, Russian texts written in Cyrillic, etc. But I\u2019ll leave those to others to analyze.\u201d So I decided to take up Swofford\u2019s challenge as it pertains to Japanese. Using Google Translate<\/a>, I romanized a news item from the Asahi<\/em> of 6 December 2009:<\/p>\n\n\n\n\n\n\n
Original<\/th>\nGoogle Translate<\/th>\n<\/tr>\n
６日午後４時３５分ごろ、東京都千代田区皇居外苑の都道（内堀通り）の二重橋前交差点で、中国からの観光客の４０代の男性が乗用車にはねられ、全身を強く打って間もなく死亡した。車は歩道に乗り上げて歩いていた男性（６９）もはね、男性は頭を強く打って意識不明の重体。丸の内署は、運転していた東京都港区白金３丁目、会社役員高橋延拓容疑者（２４）を自動車運転過失傷害の疑いで現行犯逮捕し、容疑を同致死に切り替えて調べている。<\/td>\nroku nichi gogo yon ji san go fun goro , tōkyō to chiyoda ku kōkyogaien no todō （ uchibori dōri ） no nijūbashi zen kōsaten de , chūgoku kara no kankō kyaku no yon zero dai no dansei ga jōyōsha ni hane rare , zenshin wo tsuyoku u~tsu te mamonaku shibō shi ta . kuruma wa hodō ni noriage te arui te i ta dansei （ roku kyū ） mo hane , dansei wa atama wo tsuyoku u~tsu te ishiki fumei no jūtai . marunouchi sho wa , unten shi te i ta tōkyō to minato ku hakkin san chōme , kaisha yakuin takahashi nobe tsubuse yōgi sha （ ni yon ） wo jidōsha unten kashitsu shōgai no utagai de genkō han taiho shi , yōgi wo dō chishi ni kirikae te shirabe te iru . <\/td>\n<\/tr>\n
　同署によると、死亡した男性は横断歩道を歩いて渡っていたところを直進してきた車にはねられた。車は左に急ハンドルを切り、車道と歩道の境に置かれた仮設のさくをはね上げ、歩道に乗り上げたという。さくは歩道でランニングをしていた男性（３４）に当たり、男性は両足に軽いけが。<\/td>\n dōsho ni yoru to , shibō shi ta dansei wa ōdan hodō wo arui te wata~tsu te i ta tokoro wo chokushin shi te ki ta kuruma ni hane rare ta . kuruma wa hidari ni kyū handoru wo kiri , shadō to hodō no sakai ni oka re ta kasetsu no saku wo haneage , hodō ni noriage ta to iu . saku wa hodō de ran’ningu wo shi te i ta dansei （ san yon ） ni atari , dansei wa ryōashi ni karui kega .<\/td>\n<\/tr>\n
　同署は、死亡した男性の身元確認を進めるとともに、当時の交差点の信号の状況を調べている。 <\/td>\n dōsho wa , shibō shi ta dansei no mimoto kakunin wo susumeru totomoni , tōji no kōsaten no shingō no jōkyō wo shirabe te iru . <\/td>\n<\/tr>\n
　現場周辺は東京観光のスポットの一つだが、最近はジョギングを楽しむ人も増えている。 <\/td>\n genba shūhen wa tōkyō kankō no supotto no hitotsu da ga , saikin wa jogingu wo tanoshimu hito mo fue te iru . <\/td>\n<\/tr>\n<\/table>\n

Google’s romanization algorithm does a thoroughly mediocre job compared with what a human transcriber would do. To see this, compare the following:<\/p>\n\n\n\n\n\n\n\n
Google Translate<\/th>\nhuman transcriber<\/th>\n<\/tr>\n<\/thead>\n
roku nichi gogo yon ji san go fun goro , tōkyō to chiyoda ku kōkyogaien no todō （ uchibori dōri ） no nijūbashi zen kōsaten de , chūgoku kara no kankō kyaku no yon zero dai no dansei ga jōyōsha ni hane rare , zenshin wo tsuyoku u~tsu te mamonaku shibō shi ta . kuruma wa hodō ni noriage te arui te i ta dansei （ roku kyū ） mo hane , dansei wa atama wo tsuyoku u~tsu te ishiki fumei no jūtai . marunouchi sho wa , unten shi te i ta tōkyō to minato ku hakkin san chōme , kaisha yakuin takahashi nobe tsubuse yōgi sha （ ni yon ） wo jidōsha unten kashitsu shōgai no utagai de genkō han taiho shi , yōgi wo dō chishi ni kirikae te shirabe te iru . <\/td>\nMuika gogo yo-ji sanjūgo-fun goro, Tōkyō-to Chiyoda-ku Kōkyo Gaien no todō (Uchibori dōri) no Nijūbashi-zen kōsaten de, Chūgoku kara no kankō-kyaku no yonjū-dai no dansei ga jōyōsha ni hanerare, zenshin o tsuyoku utte mamonaku shibō-shita. Kuruma wa hodō ni noriagete aruite ita dansei (rokujūkyū) mo hane, dansei wa atama o tsuyoku utte ishiki fumei no jūtai. Marunouchi-sho wa, unten-shite ita Tōkyō-to Minato-ku Shirogane san-chōme, kaisha yakuin Takahashi Nobuhiro yōgisha (nijūyon) o jidōsha unten kashitsu shōgai no utagai de genkōhan taiho-shi, yōgi o dō-chishi ni kirikaete shirabete iru.<\/td>\n<\/tr>\n
dōsho ni yoru to , shibō shi ta dansei wa ōdan hodō wo arui te wata~tsu te i ta tokoro wo chokushin shi te ki ta kuruma ni hane rare ta . kuruma wa hidari ni kyū handoru wo kiri , shadō to hodō no sakai ni oka re ta kasetsu no saku wo haneage , hodō ni noriage ta to iu . saku wa hodō de ran’ningu wo shi te i ta dansei （ san yon ） ni atari , dansei wa ryōashi ni karui kega . <\/td>\nDō-sho ni yoru to, shibō-shita dansei wa ōdan hodō o aruite watatte ita tokoro o chokushin-shite kita kuruma ni hanerareta. Kuruma wa hidari ni kyū-handoru o kiri, shadō to hodō no sakai ni okareta kasetsu no saku o haneage, hodō ni noriageta to iu. Saku wa hodō de ranningu o shite ita dansei (sanjūyon) ni atari, dansei wa ryōashi ni karui kega. <\/td>\n<\/tr>\n
dōsho wa , shibō shi ta dansei no mimoto kakunin wo susumeru totomoni , tōji no kōsaten no shingō no jōkyō wo shirabe te iru . <\/td>\nDō-sho wa, shibō-shita dansei no mimoto kakunin o susumeru to tomo ni, tōji no kōsaten no shingō no jōkyō o shirabete iru. <\/td>\n<\/tr>\n
genba shūhen wa tōkyō kankō no supotto no hitotsu da ga , saikin wa jogingu wo tanoshimu hito mo fue te iru . <\/td>\nGenba shūhen wa Tōkyō kankō no supotto no hitotsu da ga, saikin wa jogingu o tanoshimu hito mo fuete iru. <\/td>\n<\/tr>\n<\/table>\n

For the sake of comparison, I have retained Google’s Hepburn-style romanization. The following changes have been made in the text in the righthand column:<\/p>\n

    \n
  1. Misread words have been rewritten. Many involve numerals; e.g. muika<\/strong> for “roku nichi”, yo-ji<\/strong> for “yon ji”, sanjūgo-fun<\/strong> for “san go fun”. The personal name Nobuhiro <\/strong>is an educated guess, but “Nobetsubuse” is certainly wrong. Shirogane<\/strong> for “hakkin” is a place-name (N.B. Google did not produce *hakukin, indicating that the algorithm does more than just character-by-character on-yomi<\/em>).<\/li>\n
  2. False spaces and consequent misreadings have been eliminated. E.g. hanerare<\/strong> for “hane rare”, wattate ita<\/strong> for “wata~tsu te i ta”.<\/li>\n
  3. Run-together phrases have been parsed correctly. E.g. to tomo ni<\/strong> for “totomoni”.<\/li>\n
  4. Capitalization of proper nouns and the first words in sentences has been introduced.<\/li>\n
  5. Hyphens are used conservatively for prefixes and suffixes, and for compound verbs with suru<\/em>. <\/li>\n
  6. Obsolete “wo” for the particle o<\/strong> has been eliminated. (N.B. Google did not produce *ha for the particle wa<\/strong>, so “wo” for o<\/strong> is just the result of laziness.)<\/li>\n
  7. Apostrophes after n<\/strong> to indicate mora nasals in positions where they are not needed have been eliminated.<\/li>\n
  8. Punctuation has been normalized to match for romanized format and paragraph indentations have been restored.<\/li>\n<\/ol>\n

    One could make the romanized text more easily readable by restoring arabic numerals, italicizing gairaigo<\/em>, and so on. Of course, if the reporter knew that his\/her copy would be reported orally or in romanization, s\/he might have chosen different wording to avoid homophonic ambiguities. E.g., Marunouchi-sho <\/strong>could be Marunouchi Keisatsu-sho<\/strong>, though perhaps in the context of a traffic accident story, it is obvious that the suffix sho<\/strong> denotes ‘police station’. Furthermore, in a digraphic Japan, homophones might not be such as great problem. If, for instance, readers were accumstomed to seeing dōsho<\/strong> for 同所 ‘same place’, then dō-sho<\/strong> would immediately signal that something different was meant, which, given context, might be entirely sufficient to eliminate misunderstanding.<\/p>\n

    But having said all that, my guess is that the romanization function of Google Translate was programmed with some care. Rather than criticize the quality Google’s algorithm, I suggest pursuing the logical consequences of assuming that it deserves about a B+ by current standards.<\/p>\n

    Analysis<\/em><\/p>\n

    Clearly, there is a vast amount of knowledge an editor needs if s\/he wants to bring Google\u2019s result up to an acceptable level of romanization for human consumption. That minimal level, in turn, is probably a far cry from what a committee of linguists might decide would be an ideal romanization for daily use in 21st-century Japan. It is quite obvious why Google\u2019s algorithm blunders \u2014 the reasons were well understood and described long ago (e.g. in Unger 1987<\/a>) \u2014 and though the algorithm can be improved, it can never produce perfect results. Computers cannot read minds, and mindreading is ultimately what it would take to produce a flawless romanization.1<\/span><\/a>\n<\/p>\n

    Furthermore, imagine the representation of the words of the text that presumably takes shape in some form or other in the mind of the skilled reader of the original text. Given that Google\u2019s programmers are doing their best to get their computers to identify words and their forms from Japanese textual data, it is clear that readers, who achieve excellent comprehension with little or no conscious effort, must be doing vastly more. The sequence of stages \u2014 from (1) the original text to (2) the Google transcription, (3) the better edited version, (4) some future \u201cideal\u201d romanization scheme, and onward to (5) whatever the brain of the skilled reader ultimately distills and comprehends \u2014 concretely illustrates how, at each stage, different kinds of information \u2014 from the easily programmable to genuine expert knowledge \u2014 must be brought to bear on the raw data. <\/p>\n

    Of course, something similar can be said of English texts as well: like Chinese characters, orthographic words of English, even though written with letters of the roman alphabet, typically function both logographically and phonographically. The English reader has to do some work too. But how much? Think of the sequence of stages just described in reverse order. The step from the mind of an expert reader (5) to an ideal romanization (4) is short compared with the distance down to the crude level of romanization produced by Google Translate (2). Yet Google does quite a bit relative to the original text (1). It does not totally<\/em> fail, but rather makes mistakes, which, as just demonstrated, a human editor can identify and correct. It manages to find many word boundaries and no doubt could do better if the company\u2019s programmers consulted some linguists and exerted themselves more. The point is that Japanese readers must cover the whole<\/em> distance from the text to genuine comprehension, a distance that must be much greater than that traversed by the practiced reader of English, for all its quaint anachronistic spellings. With a decent, standardized roman orthography, the Japanese reader would have a considerably shorter distance to negotiate.<\/p>\n

    Note<\/em><\/p>\n

      \n
    1. Indeed, starting in the 1980s, Asahi<\/em> pioneered in the use of an IBM-designed system called NELSON (New Editing and Layout System of Newspapers) that uses large-array keyboards (descriptive input) rather than the sort of kanji henkan<\/em> methods (transcriptive input) common on personal computers and dedicated word-processing systems. Consequently, the expedient of storing the underlying roman or kana<\/em> input stream alongside the selected characters is not available for Asahi<\/em> stories. Of course, such information is routinely thrown away by many other input systems too.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      The following is a guest post by Professor J. Marshall Unger of the Ohio State University’s Department of East Asian Languages and Literatures. The challenge On 18 November 2009, Mark Swofford posted an item on his website pinyin.info criticizing the … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[113,29,112,13,28,95,126,19,31],"tags":[669,670,673,863,837],"class_list":["post-3077","post","type-post","status-publish","format-standard","hentry","category-computers","category-japanese","category-kana","category-kanji","category-languages","category-linguistics","category-romaji","category-romanization","category-writing-systems","tag-google","tag-google-translate","tag-j-marshall-unger","tag-romaji","tag-romanization"],"_links":{"self":[{"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/posts\/3077","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/comments?post=3077"}],"version-history":[{"count":34,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/posts\/3077\/revisions"}],"predecessor-version":[{"id":6802,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/posts\/3077\/revisions\/6802"}],"wp:attachment":[{"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/media?parent=3077"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/categories?post=3077"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pinyin.info\/news\/wp-json\/wp\/v2\/tags?post=3077"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}