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

More documents

Recommendations

Info

Chapter 11. Tagging and tracing Program Integrated Information 179locations. The same facts are also true for Japanese PII. Therefore the TVT testerscannot uniquely locate the source text of the inappropriate translations found inthe GUI. Our approach addresses these problems.2.3 Translation without contextTranslating PII strings in a PII file is different from translating sentences in a manual.The PII strings in a PII file do not have contexts, while the sentences in amanual do have contexts. Most of the PII strings are not complete sentences andthe length of a PII string is very short, as shown in Section 2.2.There are two helpful strategies the PII strings can be translated without contexteven though many PII strings are less than 3 words. One strategy is utilizingimplicit information coming from neighbouring PII strings in a file. The otherstrategy is referring to the previous translations from a previous version of thesoftware.The neighbourhood information and the translation for a previous versioncan help the translators to imagine the context of the PII strings. Many PII stringshave relationships to the neighboring lines. Skilled translators can reconstructthe contexts of the PII strings from the neighborhood information and producecorrect translations.Most PII translations PII files are for files with previous versions. PII stringtranslation is done with reference to the PII strings of the previous version. Theprevious version gives the translators many hints, even though it also lacks context.Translators often use the same translation when there is a pair of an unchangedoriginal and a previously translated target string.This translation method works in most cases. However, this method dependson the translators’ imagination and occasionally the translators’ guesses are incorrect.Therefore the PII translation has problems and needs a translation verificationtest (TVT) to correct the gaps and errors. This involves looking at the PIIstrings in context in the GUI. The TVT is an important part of the translationprocess.2.4 Related research on tracking PII stringsOne of the goals of this research is to find the source location of the PII stringsappearing in the GUI. To do this, we developed a utility program. The programadds a short group of ID (identification) characters in front of every PII string.The tested programs in the TVT display the ID as part of the string displayed inthe GUI. This tag is called the PII ID tag or ID tag.The Mock Translator (Muhanna 2003) and the IBM invention disclosure in(IBM 2003) are related research. The Mock Translator allows program developers
180 Naotaka Kato and Makoto Arisawato test the program for PII translation. This tool can check whether the programdisplays the various fonts of supported languages correctly. It does not support anyfunctions for translators.The invention disclosure (IBM 2003) adds a file name and a directory namefor the PII in front of the PII strings similar to the ones used in our approach. OurPII ID tag uses a configurable ID, but the disclosure uses the original names forthe ID. The names of the files (including the directory paths) can easily exceed 50characters, but such long strings cannot be handled properly by typical GUIs, andtherefore cannot be used for TVT. For example, the average length of a source filename for CATIA V5 Release 13 was 34 characters. Such file names by themselvescause many problems in a GUI, since the GUI was specifically designed to displayshort strings in those locations.The system in the disclosure (IBM 2003) assigns the file names and keys onlyto certain PII strings, whereas our approach assigns ID systematically to all of thePII, and to both the original and target language files. This systematic approach isan important point of our technique for benefiting from the PII ID tags.In the linguistic research field, our research is related to the word sense disambiguation(Ide & Veronis 1998). However, there is no research about the wordsense disambiguation for PII strings.3. The main problems that TVT testers faceIn this section we describe the main problems that TVT testers face. In Section3.1, we explain the problems in identifying the source location of a PII string. InSection 3.2, we explain the problems in referring to the original language.3.1 Problems in identifying the source locationThe TVT testers face difficulties in tracking the PII strings. When the TVT testersverify the translated PII strings according to the execution scenario of the software,they cannot identify where the strings are located in the PII files duringthe TVT. The displayed strings in the GUI have no information about where thestrings came from, whether from an external PII file in the original language, froman external PII file in the translated language, or from hard-coded strings in theprogram itself.Our research focuses on and solves this problem faced by the TVT testers.Please refer to Fig. 1 again. If a TVT tester finds that the translated ‘ ’(Japanese)is wrong and should be fixed, the tester needs to find the key for the string in a PIIfile. Then the TVT tester must find the source location of the string that needs tobe checked. In the past, the TVT tester has used a grep function of the OS or editor
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 138 and 139:
Page 140 and 141:
Page 142 and 143: 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 186 and 187: chapter 11Tagging and tracing Progr
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

Create successful ePaper yourself

Delete template?

Save as template?