Content deleted Content added
Iridescent (talk | contribs) m →Further reading: Cleanup and typo fixing, typo(s) fixed: 123-136 → 123–136 (2) |
Adding local short description: "Segmented database to aid translators", overriding Wikidata description "database storing units of language to assist the translation process" |
||
(28 intermediate revisions by 23 users not shown) | |||
Line 1:
{{Short description|Segmented database to aid translators}}
{{citations missing|date=November 2022}}
A '''translation memory''' ('''TM''') is a database that stores "segments", which can be sentences, paragraphs or sentence-like units (headings, titles or elements in a list) that have previously been translated, in order to aid human [[Translation|translators]]. The translation memory stores the [[source text]] and its corresponding translation in language pairs called “translation units”. Individual words are handled by terminology bases and are not within the domain of TM.
Software programs that use translation memories are sometimes known as '''translation memory managers''' ('''TMM''') or '''translation memory systems''' ('''TM systems''', not to be confused with a [[
Translation memories are typically used in conjunction with a dedicated [[computer
Research indicates that many [[language industry|companies producing multilingual documentation]] are using translation memory systems. In a survey of language professionals in 2006, 82.5% out of 874 replies confirmed the use of a TM.<ref name="survey"/> Usage of TM correlated with text type characterised by technical terms and simple sentence structure (technical, to a lesser degree marketing and financial), computing skills, and repetitiveness of content.<ref name="survey">Elina Lagoudaki (2006), "Translation Memory systems: Enlightening users' perspective. Key finding of the TM Survey 2006 carried out during July and August 2006. (Imperial College London, Translation Memories Survey 2006), p.16 {{cite web |url=http://www3.imperial.ac.uk/portal/pls/portallive/docs/1/7307707.PDF |title=Archived copy |
== Using
The program breaks the '''[[source text]]''' (the text to be translated) into segments, looks for matches between segments and the source half of previously translated source-target pairs stored in a '''translation memory''', and presents such matching pairs as translation full and partial '''
Some translation memory systems search for 100% matches only,
The flexibility and robustness of the matching algorithm largely determine the performance of the translation memory, although for some applications the recall rate of exact matches can be high enough to justify the 100%-match approach.
Line 29 ⟶ 32:
=== Main obstacles ===
{{
The main problems hindering wider use of translation memory managers include:
Line 43 ⟶ 46:
=== Effects on quality ===
The use of TM systems might have an effect on the quality of the texts translated. Its main effect is clearly related to the so-called "error propagation": if the translation for a particular segment is incorrect, it is in fact more likely that the incorrect translation will be reused the next time the same
There is a potential, and, if present, probably an unconscious effect on the translated text. Different languages use different sequences for the logical elements within a sentence and a translator presented with a multiple clause sentence that is half translated is less likely to completely rebuild a sentence. Consistent empirical evidences (Martín-Mor 2011) show that translators will most likely modify the structure of a multiple clause sentence when working with a text processor rather than with a TM system.
Line 49 ⟶ 52:
There is also a potential for the translator to deal with the text mechanically sentence-by-sentence, instead of focusing on how each sentence relates to those around it and to the text as a whole. Researchers (Dragsted 2004) have identified this effect, which relates to the automatic segmentation feature of these programs, but it does not necessarily have a negative effect on the quality of translations.
==Types of
* Desktop: Desktop translation memory tools are typically what individual translators use to complete translations. They are programs that a freelance translator downloads and installs on
* Server-based or
==Functions==
The following is a summary of the main functions of a translation memory.
===
==== Import ====
Line 110 ⟶ 113:
==History==
1970s is the infancy stage for TM systems in which scholars carried on a preliminary round of exploratory discussions. The original idea for TM systems is often attributed{{according to whom|date=April 2018}} to Martin Kay's "Proper Place" paper
The idea was incorporated from ALPS (Automated Language Processing Systems) Tools first developed by researcher from Brigham Young University, and at that time the idea of TM systems was mixed with a tool
The real exploratory stage of TM systems would be 1980s. One of the first
TM technology only became commercially available on a wide scale in the late 1990s,
In the 2000s, online translation services began incorporating TM. Machine translation services like [[Google Translate]], as well as professional and "hybrid" translation services provided by sites like [[Gengo]] and [[Translation Cloud#Ackuna|Ackuna]], incorporate databases of TM data supplied by translators and volunteers to make more efficient connections between languages provide faster translation services to end-users.<ref>[https://techcrunch.com/2016/11/22/googles-ai-translation-tool-seems-to-have-invented-its-own-secret-internal-language/ Google's AI translation tool seems to have invented its own secret internal language] Devin Coldewey, TechCrunch, November 22, 2016</ref>
Line 149 ⟶ 152:
===XLIFF===
'''[[XLIFF|XML Localisation Interchange File Format]]''' (XLIFF) is intended to provide a single interchange file format that can be understood by any localization provider. [[XLIFF]] is the preferred way<ref>{{Cite web|title=DITA Translation SC {{!}} OASIS|url=https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-translation|access-date=2021-01-29|website=www.oasis-open.org}}</ref><ref>{{Citation|last=Roturier|first=Johann|title=XML
</ref>
Line 157 ⟶ 160:
===xml:tm===
{{Main article|xml:tm}}
The xml:tm (XML-based Text Memory) approach to translation memory is based on the concept of text memory which comprises author and translation memory.<ref>{{cite web|title=OAXAL—What is it and why should I care|url=http://www.infomanagementcenter.com/enewsletter/200808/second.htm|work=CIDM Information Management News|
===PO===
Line 187 ⟶ 190:
* [https://web.archive.org/web/20050123123221/http://ecolore.leeds.ac.uk/downloads/2003.05_bdue_survey_analysis.doc Ecolore survey of TM use by freelance translators (Word document)]
* [https://doi.org/10.1007%2Fs10590-008-9033-6 Power Shifts in Web-Based Translation Memory]
[[Category:Computer-assisted translation]]
[[Category:Translation databases]]
|