{"id":94,"date":"2017-07-26T12:00:00","date_gmt":"2017-07-26T16:00:00","guid":{"rendered":""},"modified":"2018-10-26T11:00:52","modified_gmt":"2018-10-26T15:00:52","slug":"for-project-managers-and-translators","status":"publish","type":"post","link":"https:\/\/www.ata-divisions.org\/JLD\/2017\/07\/26\/for-project-managers-and-translators\/","title":{"rendered":"For Project Managers and Translators"},"content":{"rendered":"

Japanese Orthographic Variants in CAT Tool Based Translation
and What You Can Do About It — Part 1 of 2<\/h4>\n
by JLD Member Noriko Nevins,<\/o:p><\/div>\n
ATA-Certified (E>J) Translator<\/o:p><\/div>\n
<\/div>\n
<\/div>\n
This writing is for Project Managers unfamiliar with the intricacies of Japanese orthographic rules and Japanese translators who use CAT tools, especially SDL Trados Studio. In this article I identify the problems <\/span>Japanese orthographic rules can pose in CAT-tool-based translation, and what can project managers and translators can do to ensure spelling consistency in the TM. I also describe some of the <\/span>different tools available and highlight those I found the easiest and simplest to implement in terms of cost and steps involved.<\/span><\/div>\n

<\/p>\n

<\/o:p><\/div>\n

<\/p>\n

                                                  <\/span><\/o:p><\/div>\n
Part Two of “For Project Managers and Translators: Japanese Orthographic Variants in CAT Tools Based Translation and What You Can Do About It” will be posted later this year. However, look out for the full version of this article in the PDF version of the JLD Times coming soon!<\/div>\n
<\/span><\/div>\n
<\/span><\/div>\n

<\/a><\/p>\n

Nearly three decades ago, the first CAT tools were introduced to the translation industry. Many<\/span>translation agencies now utilize their choice of CAT tools in-house, and require freelance translators they work with to use the same tools. When these translation agencies send a new project package to a translator, they often lock segments for which translations already exist in their translation memory (TM). The idea is that by locking these segments, the segments will not get translated again unnecessarily, thus saving on translation cost.<\/o:p><\/div>\n
<\/div>\n
In an ideal world, the translator needs to do nothing to the locked segments. However, in English-into-Japanese translation projects, I frequently find locked segments that contain the same words spelled differently, i.e., I find orthographic variants within the same pre-translated file. If a translator notices variants in the spellings, she must address them in the same way she would address with terminology inconsistencies: Alert the project manager, determine which spelling variant is desirable for the project and the end client, and correct all unwanted versions in the project.<\/o:p><\/div>\n
<\/div>\n
Because no <\/span>two Japanese persons spell all words completely in the same way unless they are given the same spelling guideline, and because orthographic rules have not been standardized in Japanese, this tends to happen quite frequently in into-Japanese translation projects. As I worked with many translators and clients\u2019 reviewers over the years, I began to wonder whether spelling differences among Japanese individuals are much greater than those among users of other languages. I researched a little bit and found numerous academic papers touching the subject, noting that it poses a significant challenge to machine translation, search engine optimization, database building and searching, teaching Japanese as a second language, etc. One study shows Japanese orthographic variants found in books, websites and magazines make up nearly 10% of all morphemes in the text. [1]<\/span><\/span><\/span><\/span><\/a> Another paper mentions that while most English orthographic variants tend to be rare, archaic or loan words, Japanese orthographic variants are frequently found in common words that are used today. It also found that number of variants pairs\/sets in Japanese is over 50,000, which is twice the number of English orthographic variants. [2]<\/span><\/span><\/span><\/span><\/a> <\/o:p><\/div>\n
<\/div>\n
In the modern Japanese writing system, a word could be written with only hiragana, katakana, or in different combinations of kanji and hiragana, and they all may be commonly accepted spellings. Unlike some other languages, there is no reliable and unified standard spelling guideline for written Japanese. Furthermore, the version of spelling a person would use to write a specific word depends on the literacy and background of the individual, which is I think the compilation of the following factors:<\/o:p><\/div>\n
<\/div>\n
\u00b7         <\/span><\/span><\/span>Literary environment of the person\u2019s family and community in which the individual was raised.<\/o:p><\/span><\/div>\n
\u00b7         <\/span><\/span><\/span>Since over time the Ministry of Education made changes to the use of kana and the kanji to be taught, the period during which the individual was in school in Japan.<\/o:p><\/span><\/div>\n
\u00b7         <\/span><\/span><\/span>Books, newspapers and magazine the person read growing up. Japanese newspapers and publishers enforce internal style guides within each company or publication. Fiction and non-fiction writers often have their own unique spelling preferences; one is influenced by the style of text one frequently reads.<\/o:p><\/span><\/div>\n
\u00b7         <\/span><\/span><\/span>The individual\u2019s job history. A Japanese person adopts different spelling conventions depending on the industry, employer, and occupation in which she has worked.<\/o:p><\/span><\/div>\n
\u00b7         <\/span><\/span><\/span>Language changes (e.g. neologisms, spelling convention changes, etc.) reflecting changes of the times the person has been exposed to. <\/o:p><\/span><\/div>\n
<\/div>\n
So, when multiple Japanese translators have been involved in an into-English translation project, spelling variants inevitably make their way into the TM unless a clear style guide is given to the translators and editors at the outset of the project. Here\u2019s one simple example of spelling variants found in a translation project.  <\/span>(I changed the sentences slightly for clarity.)<\/o:p><\/div>\n
<\/div>\n
Example 1<\/o:p><\/div>\n\n\n\n\n\n
\n
<\/div>\n<\/td>\n
\n
Source Text (English)<\/o:p><\/div>\n<\/td>\n
\n
<\/div>\n<\/td>\n
\n
Target Text (Japanese)<\/o:p><\/div>\n<\/td>\n<\/tr>\n
\n
A<\/o:p><\/div>\n<\/td>\n
\n
Thank you for your cooperation!<\/o:p><\/div>\n<\/td>\n
\n
100% match, locked<\/o:p><\/div>\n<\/td>\n
\n
\u3054\u5354\u529b\u3042\u308a\u304c\u3068\u3046<\/span>\u3054\u3056\u3044\u307e\u3059\u3002<\/span><\/o:p><\/span><\/div>\n<\/td>\n<\/tr>\n
\n
B<\/o:p><\/div>\n<\/td>\n
\n
Thank you for your time!<\/o:p><\/div>\n<\/td>\n
\n
100% match, locked<\/o:p><\/div>\n<\/td>\n
\n
\u304a\u6642\u9593\u3092\u5272\u3044\u3066\u3044\u305f\u3060\u304d\u6709\u96e3\u3046<\/span>\u3054\u3056\u3044\u307e\u3059\u3002<\/span><\/o:p><\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n
The document was a survey of physicians. Here, the word \u201cThank you\u201d (highlighted in yellow) is spelled differently in two segments found within same sheet. Neither of them is wrong. Both are accepted in Japan as correct spellings, although the hiragana-only version appears to be more commonly used nowadays. So, the Translator A may have been younger than Translator B. Both segments came from past translation projects that did go through review, approval and finalization processes. In this project, only two variants for \u201cThank you\u201d were found in a single file. So, it was easy to unify them.<\/o:p><\/div>\n
<\/div>\n
Here\u2019s another example. This is about a medical term. <\/o:p><\/div>\n
<\/div>\n
Example 2<\/o:p><\/div>\n\n\n\n\n\n
\n
<\/div>\n<\/td>\n
\n
Source Text (English)<\/o:p><\/div>\n<\/td>\n
\n
<\/div>\n<\/td>\n
\n
Target Text (Japanese)<\/o:p><\/div>\n<\/td>\n<\/tr>\n
\n
A<\/o:p><\/div>\n<\/td>\n
\n
Carotid Ultrasound<\/o:p><\/div>\n<\/td>\n
\n
100% match, locked<\/o:p><\/div>\n<\/td>\n
\n
\u9838\u52d5\u8108<\/span>\u8d85\u97f3\u6ce2\u691c\u67fb<\/span><\/o:p><\/span><\/div>\n<\/td>\n<\/tr>\n
\n
B<\/o:p><\/div>\n<\/td>\n
\n
About Carotid Ultrasound<\/o:p><\/div>\n<\/td>\n
\n
100% match, locked<\/o:p><\/div>\n<\/td>\n
\n
\u981a\u52d5\u8108<\/span>\u8d85\u97f3\u6ce2\u691c\u67fb\u306b\u3064\u3044\u3066<\/span><\/o:p><\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n
An example like this can sometimes be found in a hospital\u2019s patient guide. Different kanjis are used for the first character of the word \u201ccarotid.\u201d In this case, Translator A\u2019s <\/span>\u9838<\/span>is the formal version used by medical professionals. Translator B uses <\/span>\u981a<\/span> <\/span>instead, which is a simplified version of the same kanji and used mostly by lay people. The translator who used the latter might have been used to using the simplified version, or the Japanese input system she was using happened to have <\/span>\u981a\u52d5\u8108<\/span> <\/span>ahead of <\/span>\u9838\u52d5\u8108<\/span> in the order of kana-to-kanji conversion candidates. In this case too, it was easy to fix because there were only two variants.<\/o:p><\/span><\/div>\n
<\/div>\n
The next example is not so simple. The end client was in international catering business and the project was to translate their menus. A tricky thing with the Japanese language is that most vegetables, fruits and seafood can be spelled in two or three different ways. Who would have thought food could make translators\u2019 job so complicated! Below are examples of the food names that showed up as part of various dish names in pre-translated segments in a series of menus.<\/o:p><\/span><\/div>\n
<\/div>\n
Example 3<\/o:p><\/span><\/div>\n
Carrot (ninjin): <\/span>\u306b\u3093\u3058\u3093<\/span>, <\/span>\u30cb\u30f3\u30b8\u30f3<\/span>, <\/span>\u4eba\u53c2<\/span><\/o:p><\/span><\/div>\n
Cucumber (kyuuri): <\/span>\u304d\u3085\u3046\u308a<\/span>, <\/span>\u30ad\u30e5\u30a6\u30ea<\/span>, <\/span>\u80e1\u74dc<\/span><\/o:p><\/span><\/div>\n
Eggplant (nasu): <\/span>\u306a\u3059<\/span>, <\/span>\u30ca\u30b9<\/span>, <\/span>\u8304\u5b50<\/span><\/o:p><\/span><\/div>\n
Tuna (maguro): <\/span>\u307e\u3050\u308d<\/span>, <\/span>\u30de\u30b0\u30ed<\/span>, <\/span>\u9baa<\/span><\/o:p><\/span><\/div>\n
Shrimp (ebi): <\/span>\u3048\u3073<\/span>, <\/span>\u30a8\u30d3<\/span>, <\/span>\u6d77\u8001<\/span><\/o:p><\/span><\/div>\n
Squid (ika): <\/span>\u3044\u304b<\/span>, <\/span>\u30a4\u30ab<\/span>, <\/span>\u70cf\u8cca<\/span><\/o:p><\/span><\/div>\n
<\/div>\n
How did all these variants end up in the TM? We could think of different possibilities. One is that the editor and the client reviewer involved in the past projects from which the TM was created or updated, may not always have been the same set of people, and may not have provided with any style guide or guidelines. So, every time a new member, especially a translator, joined the team, the member might have introduced new variants. It\u2019s likely to have been unintentional, and the spelling choice might have been based on personal preference or just because she was simply used to using the specific spelling. Another possibility is that a single translator might have used more than one variant as a result of forgetting what variant she used previously. Or maybe the individual just decided to switch variants over the course of an ongoing project.<\/o:p><\/div>\n
<\/div>\n
In cases like the examples above, if spelling inconsistencies go uncorrected, it would give end users of the translations an impression that the job was poorly done without much care or thought. It\u2019s especially risky when a long document is divided among multiple translators and no unification of spellings is done before the document is delivered to the end client.<\/o:p><\/div>\n
<\/div>\n
So, what could project managers and translators do to minimize this problem and improve TM integrity? I\u2019ll discuss possible solutions in Part 2: Japanese Orthographic Variants in CAT Tool based Translation and What You Can Do About It.<\/i><\/div>\n

<\/p>\n


<\/p>\n
<\/p>\n
\n
[1]<\/span><\/span><\/span><\/span><\/span><\/a> <\/span>\u30b3\u30fc\u30d1\u30b9\u306b\u57fa\u3065\u304f\u73fe\u4ee3\u8a9e\u8868\u8a18\u306e\u3086\u308c\u306e\u8abf\u67fb<\/span> <\/span>\u2015<\/span> BCCWJ <\/span>\u30b3\u30a2\u30c7\u30fc\u30bf\u3092\u8cc7\u6599\u3068\u3057\u3066<\/span> <\/span>\u2015<\/span>\u5c0f\u690b\u79c0\u6a39<\/span>(<\/span>\u56fd\u7acb\u56fd\u8a9e\u7814\u7a76\u6240\u8a00\u8a9e\u8cc7\u6e90\u7814\u7a76\u7cfb<\/span>), Corpus-Based Survey of the Orthographic Variation in Contemporary Japanese: Analysis of the BCCWJ-Core<\/o:p><\/span><\/div>\n
Hideki Ogura (Dept. Corpus Studies, NINJAL). Available at: <\/span>https:\/\/www.ninjal.ac.jp\/event\/specialists\/project-meeting\/files\/JCLWorkshop_no1_papers\/JCLWorkshop2012_42.pdf<\/span><\/a> [Accessed January 16th, 2017]<\/o:p><\/span><\/div>\n<\/div>\n
\n
[2]<\/span><\/span><\/span><\/span><\/span><\/a> Otmakhova, J, Orthographical variants in modern Japanese, Tomsk Polytechnic University. Available at: <\/span>https:\/\/online.sfsu.edu\/icplj\/conference\/ICPLJ6%20Papers\/Otmakhova.pdf<\/span><\/a> [Accessed January 16th, 2017]<\/o:p><\/span><\/div>\n
<\/div>\n
<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Japanese Orthographic Variants in CAT Tool Based Translationand What You Can Do About It — Part 1 of 2 by JLD Member Noriko Nevins, ATA-Certified (E>J) Translator This writing is for Project Managers unfamiliar with the intricacies of Japanese orthographic rules and Japanese translators who use CAT tools, especially SDL Trados Studio. In this article […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[14,12,13,26],"tags":[],"_links":{"self":[{"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/posts\/94"}],"collection":[{"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/comments?post=94"}],"version-history":[{"count":1,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/posts\/94\/revisions"}],"predecessor-version":[{"id":206,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/posts\/94\/revisions\/206"}],"wp:attachment":[{"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/media?parent=94"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/categories?post=94"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ata-divisions.org\/JLD\/wp-json\/wp\/v2\/tags?post=94"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}