12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 2. Interactive reference grammars 35Example (14) shows a German nom<strong>in</strong>al phrase where the nom<strong>in</strong>al head is deleted.In the English orig<strong>in</strong>al a substitution is used to express the same mean<strong>in</strong>g. S<strong>in</strong>cesubstitution does not work <strong>for</strong> German (see above), deletion seems to be anotherstrategy to translate this structure. In example (15), we f<strong>in</strong>d two Germanverbs (danken (thank) andtun (do)), the second subject is, however, deleted. Inthe English orig<strong>in</strong>al the subject we is repeated <strong>for</strong> the second verb. The samephenomenon can be observed <strong>in</strong> example (16): The English orig<strong>in</strong>al repeats thewords the way we, which are deleted <strong>in</strong> the German translation. In both examples,German is more elliptical express<strong>in</strong>g the cohesive l<strong>in</strong>ks implicitly, whereasEnglish uses repetitions express<strong>in</strong>g the lexical cohesion more explicitly. These concordancesshow that the English-German corpus can also be used <strong>in</strong>versely help<strong>in</strong>gtranslators to f<strong>in</strong>d compensations <strong>for</strong> German constructions which do not exist<strong>in</strong> English.4. Conclud<strong>in</strong>g remarks and outlookThe need <strong>for</strong> l<strong>in</strong>guistically annotated corpora is observed across all branches ofl<strong>in</strong>guistics, and the translation branch is no exception. There are certa<strong>in</strong>ly researchquestions which do not require such a detailed l<strong>in</strong>guistic analysis, but which canbe resolved us<strong>in</strong>g unannotated data or automatic annotation without the burdenof construct<strong>in</strong>g a big and complex language resource <strong>in</strong> advance. However, translationproblems result<strong>in</strong>g from the specificity of a language or a register need amore detailed l<strong>in</strong>guistic analysis <strong>in</strong> order to be answered.In this chapter, we have suggested that monol<strong>in</strong>gual and multil<strong>in</strong>gual treebankscan assume the role of grammatical reference works <strong>for</strong> translation tra<strong>in</strong><strong>in</strong>gand practice. In order <strong>for</strong> corpora to serve this purpose, they need to be enrichedwith l<strong>in</strong>guistic <strong>in</strong><strong>for</strong>mation (Section 2). We have discussed the notions ofmonol<strong>in</strong>gual and parallel treebank<strong>in</strong>g and <strong>in</strong>troduced some of the most importanttreebanks. In Section 3, we have shown that l<strong>in</strong>guistic annotation can makea corpus a valuable resource <strong>for</strong> deal<strong>in</strong>g with some typical translation problems.Offer<strong>in</strong>g the possibility to search <strong>for</strong> grammatical constructions (such as word ordervariation, cleft<strong>in</strong>g, rais<strong>in</strong>g constructions as well as substitutions and deletions)these treebanks are a much more powerful resource compared to parallel corporaof raw texts. And contrast<strong>in</strong>g them to usual (pr<strong>in</strong>ted) reference grammars, theconcordances generated on the basis of the treebanks are far more comprehensiveand exhaustive. Thus, the CroCo Corpus as well as the Penn and TiGer Treebanksprove to provide a wealth of <strong>in</strong><strong>for</strong>mation <strong>for</strong> the translation of typologicallanguage problems.Besides typologically motivated translation solutions, also examples <strong>for</strong> registerspecificlanguage use and their appropriate translations (i.e., register-specific

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!