Topics in Language Resources for Translation ... - ymerleksi - home

More documents

Recommendations

Info

chapter 11Tagging and tracing ProgramIntegrated InformationNaotaka Kato, and Makoto ArisawaTranslation Services Center, IBM Japan, Ltd. / Faculty of Graduate Schoolof Media and Governance, Keio UniversityThere are two main types of translation involving computer programs. One involvesmanuals and the other involves Program Integrated Information (PII). Thischapter focuses on PII translation. PII translation is substantially different fromordinary text translation. PII is separated out of the programs into externalisedtext resource files to allow for translation outside the program development laboratory.The contexts of the operations have been discarded. The translators haveto translate phrases and words without context in these text resource files. TheTranslation Verification Test (TVT), which is done with the normal operations ofthe program, compensates for the lack of context during translation. If the TVTtester finds an inappropriate translation in the GUI (Graphical User Interface),the file it came from and which line in the file is unknown. We have developed autility program to make it easy to find a source location. The utility adds a shortgroup of ID characters in front of every PII string. We used this systematic approachfor CATIA ®1 and found many advantages, such as locating the hard-codedstrings that are the biggest problems in program internationalisation. This ID canbe inserted independently of program development. We also developed a utilityprogram that helps TVT testers refer to both the original and target PII stringsas pairs. This chapter describes the approach in detail. In addition, this chapterpresents statistics about PII files. This important statistical information has notbeen considered in the program internationalisation communities.1. IntroductionProgram internationalisation often requires software developers to translate thestrings of programs into nine or more languages. This translation task is notcarried out in a software development laboratory but in an organisation thatspecialises in translation. If the text strings might need to be translated, the1. CATIA, a CAD/CAM program, is a registered trademark of Dassault Systemes.
174 Naotaka Kato and Makoto Arisawadevelopment laboratory externalises the strings from the programs into the text resourcefiles called PII (Program Integrated Information) files. The PII file includesthe keys and the isolated text strings. The isolated strings are called PII strings. Theprograms have the keys and use their corresponding strings (Deitsch 2001; IBM2004; Dr. International 2003; Green 2005). The translators have to translate thePII strings in each file. They often cannot provide good translations because manyPII strings are short and lack context. Therefore a verification test phase compensatesfor gaps in the translations. This verification test is called a TVT (TranslationVerification Test). The testers work with the target software and check the validityof the translated PII strings as they are displayed in the GUI in each context.The current internationalisation process causes difficulties for the translatorsand the TVT testers. One of the big problems is that TVT tester cannot find thesource location of the externalised text found in a GUI message. This chapteraddresses this TVT problem and proposes a solution.Conventionally the testers have used a ‘grep’ function of the OS or editor programto find the source location in the PII files when they need to fix a translatedstring. The grep function requires a long time when checking a large number offiles. The TVT testers cannot identify the source location if identical strings appearwith different keys. One of the goals of our work is to find the locations of suchstrings in the PII files effectively and efficiently. To achieve this goal, we developedautilityprogramtomakeiteasytofindthesourcekeyofthePIIstringdisplayedin the GUI. Another goal of this research is to help TVT testers refer to both theoriginal (English) and target (Japanese) PII strings as pairs. To achieve this goal,we developed a utility program to produce a comprehensive index file showing allof the information about the PII strings in both languages.We confirmed the effectiveness of the utilities by actually using them for theJapanese TVTs of the CATIA PII translation. We also discovered many useful waysto use our utilities while performing these TVTs. One of the benefits of using theseutilities is to expose the hard-coded strings in the tested program. A hard-codedstring is called the “granddaddy” of all TVT errors and is the most difficult sourcestring to find (Kehn 2002). The introduction of our utilities reduced the time tofind the string locations in the PII files from 40 hours to one or two hours for theCATIA TVTs.We explain the background of our research by focusing on the PII translationprocess and a statistical analysis of the characteristics of PII strings in Section 2.In Section 3, we explain the problems that the TVT testers face in conventionalTVT. In Section 4, we explain our approach to solving the problems in TVT. InSection 5, we describe the details of our implementation so that programmersmay implement our approach in their own systems. Most readers may prefer toskip Section 5. Finally, Section 6 concludes this chapter.
Page 3 and 4:
Benjamins Translation Library (BTL)
Page 5 and 6:
8 TMThe paper used in this publicat
Page 7 and 8:
VITopics in Language Resources for
Page 9 and 10:
VIII Topics in Language Resources f
Page 11 and 12:
XTopics in Language Resources for T
Page 13 and 14:
XIITopics in Language Resources for
Page 15 and 16:
2 Lynne Bowker and Michael Barlowde
Page 17 and 18:
4 Lynne Bowker and Michael BarlowFi
Page 19 and 20:
6 Lynne Bowker and Michael Barlow2.
Page 21 and 22:
8 Lynne Bowker and Michael BarlowOn
Page 23 and 24:
10 Lynne Bowker and Michael Barlow4
Page 25 and 26:
12 Lynne Bowker and Michael Barlowb
Page 27 and 28:
14 Lynne Bowker and Michael Barlows
Page 29 and 30:
16 Lynne Bowker and Michael Barlowp
Page 31 and 32:
18 Lynne Bowker and Michael Barlowt
Page 33 and 34:
20 Lynne Bowker and Michael Barlowg
Page 35 and 36:
22 Lynne Bowker and Michael BarlowM
Page 37 and 38:
24 Silvia Hansen-Schirraphenomenon;
Page 39 and 40:
26 Silvia Hansen-Schirratreebank pr
Page 41 and 42:
28 Silvia Hansen-Schirracurrently a
Page 43 and 44:
30 Silvia Hansen-Schirrawhichaltern
Page 45 and 46:
32 Silvia Hansen-Schirra(1) We cont
Page 47 and 48:
34 Silvia Hansen-Schirrarealisation
Page 49 and 50:
36 Silvia Hansen-Schirratranslation
Page 52 and 53:
chapter 3Corpora for translator edu
Page 54 and 55:
Chapter 3. Corpora for translator e
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68:
Page 71 and 72:
58 Belinda Maiahindsight, one can n
Page 73 and 74:
60 Belinda Maiabeen translated by m
Page 75 and 76:
62 Belinda Maiastudy reformulations
Page 77 and 78:
64 Belinda MaiaSearchablecorporaenc
Page 79 and 80:
66 Belinda Maia- Find definition ca
Page 81 and 82:
68 Belinda MaialishaEuropeanMaster
Page 83 and 84:
70 Belinda MaiaMaia, B. and L. Sarm
Page 85 and 86:
72 Carme Colominas and Toni Badiadi
Page 87 and 88:
74 Carme Colominas and Toni Badiala
Page 89 and 90:
76 Carme Colominas and Toni Badiath
Page 91 and 92:
78 Carme Colominas and Toni Badiath
Page 93 and 94:
80 Carme Colominas and Toni BadiaTa
Page 95 and 96:
82 Carme Colominas and Toni BadiaAs
Page 97 and 98:
84 Carme Colominas and Toni BadiaFi
Page 99 and 100:
86 Carme Colominas and Toni Badiaco
Page 101 and 102:
88 Carme Colominas and Toni BadiaVa
Page 103 and 104:
90 Rachélle GautonIzwaini (2003:17
Page 105 and 106:
92 Rachélle Gautonneeded by the Ba
Page 107 and 108:
94 Rachélle GautonThese electronic
Page 109 and 110:
96 Rachélle Gautonthat of Bantu la
Page 111 and 112:
98 Rachélle GautonSeeagainFig.1for
Page 113 and 114:
100 Rachélle GautonLocke, translat
Page 115 and 116:
102 Rachélle GautonHaving to work
Page 117 and 118:
104 Rachélle Gautonmore, after suc
Page 119 and 120:
106 Rachélle GautonMcEnery, A. and
Page 121 and 122:
108 Marie-Josée de Saint Roberta c
Page 123 and 124:
110 Marie-Josée de Saint Robertpre
Page 125 and 126:
112 Marie-Josée de Saint Robertlef
Page 127 and 128:
114 Marie-Josée de Saint Robertcap
Page 129 and 130:
116 Marie-Josée de Saint Robertinf
Page 131 and 132:
118 Marie-Josée de Saint Roberttra
Page 134 and 135:
chapter 8Global content managementC
Page 136 and 137: Chapter 8. Global content managemen
Page 148 and 149: chapter 9BEYTransA Wiki-based envir
Page 150 and 151: Chapter 9. BEYTrans 137Trans system
Page 152 and 153: Chapter 9. BEYTrans 1391. Facilitat
Page 154 and 155: Chapter 9. BEYTrans 141lators to ch
Page 156 and 157: Chapter 9. BEYTrans 1435.2 Translat
Page 158 and 159: Chapter 9. BEYTrans 1456. BEYTrans:
Page 160 and 161: Chapter 9. BEYTrans 1476.2.2 Multil
Page 162 and 163: Chapter 9. BEYTrans 149Bey, Y., C.
Page 164 and 165: chapter 10Standardising the managem
Page 166 and 167: Chapter 10. Standardising multiling
Page 188 and 189: Chapter 11. Tagging and tracing Pro
Page 208 and 209: chapter 12Linguistic resources and
Page 210 and 211: Chapter 12. Linguistic resources an
Page 228 and 229: IndexAAfrican language translatorX,
Page 230 and 231: Index 217Expert Advisory Group onLa
Page 232 and 233: Index 219open standards 206, 208,21
Page 234 and 235: Benjamins Translation LibraryA comp
Page 236:
27 Beylard-Ozeroff, Ann, Jana Král
show all

Topics in Language Resources for Translation ... - ymerleksi - home

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?