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

More documents

Recommendations

Info

Chapter 11. Tagging and tracing Program Integrated Information 187important role for the ID tag. We will explain the architecture of this prefix moreprecisely in this section. The prefix J7d signifies Japanese, Release 17, d build forthis ID tag. Here is the complete format of an ID tag:(PrefixFilenumber.Linenumber)Here are the semantics of the elements:“(”: Start of the ID tag“)”: End of the ID tag“Prefix”: Prefix“Filenumber”: The file number of the PII file that includes the string. The filenumber is assigned within each language directory.“.”: Separator between the file number and the line numberThe parentheses not only separate the ID tag from the PII strings, but also makeit possible to recognise concatenated PII strings in the GUI. We will explain the“Prefix” more fully in the next section. To keep the ID tags short, we did not insertany character to separate the “Prefix” from “Filenumber”. We used decimalnumbers for the file numbers (Filenumber) and the line numbers (Linenumber).The average length of the PII file names for CATIA is 28 characters and the averagekey length for CATIA is 34 characters. The GUI elements often do not have spacefor very long names for the PII strings. The length of an ID tag needs to be shortto limit the space that it occupies in the GUI. We considered using hexadecimalnumbers to shorten the length of the ID tags. The hex numbers would reduce thelength when the file numbers are large. However, this called for a separator betweenthe prefix and the file number and actually increased the average length ofthe ID tag. The readability of the ID tag was also greatly decreased as hexadecimal.Therefore, we used ordinary decimal numbers.We prepared the comprehensive index files to help the TVT testers find specificPII keys in the PII files with or without ID tags. The format of the ID tag allowsa TVT tester to search for the location of the ID in the comprehensive index file.The comprehensive index file uses a plain text format, and it is a list of all of thePII for both the original and target languages. We will describe the comprehensiveindex file more fully in Section 5.5.5.3 Prefix architecture of ID TagsA TVT tester can assign any ASCII strings to the prefixes when an ID tag is used inTVT. However, the TVT tester must conform to the prefix architecture. The prefixarchitecture is an important feature of the ID tag. Without it, the value of the IDtags would be reduced.
188 Naotaka Kato and Makoto ArisawaThe main function of the prefix is grouping. The group is not only languagegroup, but also levels of strings including the version/build numbers etc. Thegrouping function is used to identify the language sources of the PII files. Thefunction identifies whether or not the string was located in the original language(English) PII or in the target language (Japanese) PII. The displayed strings donot always identify the language source unless the ID tag is used, because the targetlanguage may include the original language without a change. For example, ifan English identifier such as “E7d240.7” is included in a prefix and is shown in aJapanese GUI, this means that no JapanesePIIkeywasfoundbytheprograms.Theprogram uses an English PII string instead of a Japanese PII string if it cannot findthe Japanese PII key. One possible cause of such errors is that development laboratorymight have failed to send the corresponding English PII file to the TranslationServices Center.The grouping function may include additional information identifying thelevels of the PII files such as the version or release numbers of the PII files andID tag build numbers for the files. We can have many levels of PII files within eachversion or release, which calls for tracking the ID tag build numbers.The prefixes must not include the characters used to separate the elements inthe ID tag format, such as parentheses or the period. The last letter of the prefixmust not be a numeric character. If the last letter was a number, then the userscould not see where the file numbers begin.The current prefix format for CATIA is as follows:PII language (One character): e.g., E is used for English, J is used for JapaneseRelease/Version (One numeric character): e.g., 5 means release 15. The use ofID tags began after release 10, so we ignored the “1” to shorten the ID tags.PII ID tag build number (One lowercase alphabetic character): e.g., “a” meansthe first build.The addid.pl program included a function to replace the separator “.” with anothercharacter according to a table. The table is plain text and has pairs of text strings.Each pair maps a key with its file name to a character such as “:”, “_”, “.”. Themapping table file is prepared separately before the addid.pl is executed. If there isno mapping table file, the default separator “.” is used. For example, if a PII stringfor a key is being updated from the previous version, then the key has mappinginformation for a colon. If not, it uses the default mapping to a period. Therefore,if the ID tag is “(J7d240:7)”, it shows that the string is being updated from theprevious version. Greater attention needs to be paid to such translations. If a keywas created in the latest version, then the key has mapping information to theunderscore and the ID tag becomes “(J7d240_7)”. Then the TVT tester must checkwhetherornotthetranslationisappropriate.
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:
Page 144 and 145:
Page 146 and 147:
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

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

Delete template?

Save as template?