A match that has a score of 100%. A 100% match is always an exact match; however, not all exact matches are 100% matches (if the translation memory or translation unit is penalised, the score is reduced.)
A feature from the Translator’s Workbench that allows you to assess the number of translation matches in a document for translation by comparing the document with an existing translation memory.
In SDL TMs, the matching of source segments in a document with segments in a translation memory when the segments only differ in terms of a different acronym, date, number or other recognised token.
Translation without human input – sometimes called machine translation.
A match that takes into account the context within which the match occurs. Usually this refers to the surrounding segments. A context match is even more likely to be correct than a 100% match. There are different kinds of context match, depending on which aspects of context are taken into account (for example, formatting).
A match in relation to every aspect of a fragment of text: characters, punctuation and formatting. In an exact match, the text in the surrounding source segments might be different from the text surrounding the entry in a TM (by contrast, a context match requires the same surrounding text).
A match that has a score of less than 100%, e.g. a 75% match or a 90% match. For a translator, translating a segment that has a fuzzy match is typically easier than translating a segment that has no match but more difficult than translating an exact match. A fuzzy match requires more careful consideration and usually has to be edited.
A source language and a target language, for example English to French, or English (GB) to French (Swiss).
An alternative version of a language used in a specific culture or country, e.g. German as used in Germany (de) and German as used in Austria (de-AT).
An equivalence between two segments of text, usually between a segment of the text being translated and a source segment of a translation memory unit. Matches are assigned a match score between the fuzzy match threshold and 100%.
In SDL Trados Studio, is a context match that compares an updated source text with previously translated files rather than a translation memory.
A project contains a collection of source language files and associated files (resource files), which the SDL TM Server manages as a unit. All files within a project have the same source language but can be translated into multiple languages. Unit costs for translation are defined per project and for each target language. Each project goes through various workflow stages (e.g. translation, review, sign-off) before completion.
Pseudo-translation is a procedure (mainly used in software localisation) that shows what a document will look after translation and how much extra engineering work will be required before the actual translation is done. This can help in the planning of a project to set appropriate estimates and expectations.
Additional material or documents intended to inform a translator’s choices in terms of terminology, style, register, etc. when translating a text. It can also be useful when planning a project, gauging hoe much work will be involved and and setting appropriate estimates.
An occurrence of a segment that has been translated previously. Usually the term refers to repetitions within one translatable file, but sometimes it can be used to refer to repetitions across a number of files.
The process of comparing content to be translated with past translations in order to assess the cost and the effort involved.
The file format and file extension used by SDL Trados Studio files. It is compliant with version 1.2 of the XLIFF standard, with some added standard-compliant extensions.
A portion of text and a single translation unit for the purposes of finding a match in a translation memory. A segment often contains a single sentence. Translation memories record translations segment by segment, and segments are also the unit used for matching new text with saved translations. In a translation editor, each segment is displayed on a separate row.
A keyword assigned to a portion of text; used to specify text attributes (e.g. bold, italics, etc.) or text flow attributes (e.g. page breaks). Tags can be categorised into the following overlapping categories: inline or structure, standalone or one of a tag pair, translatable or non-translatable.
Refers to the language a project is to be translated into. For example, if your project involves the translation of a manual from English into Spanish, Spanish is the target language.
An XML standard, published as ISO 30042, for the interchange of terminology data, including detailed lexical information.
Apart from our standard qualification requirements, all our translators are rigorously tested in relation to their native and target languages as well as their areas of expertise. In addition, our reviewers check the quality of every translation. We also have editors available to further check for grammar, style, punctuation, etc. This means that the translation you receive will have been examined by at least three people, including a native speaker and professional editor for each language. The combination of superior quality and the best prices gives us a clear advantage over other translation service providers.
TBX is a Terminology Markup Language. It is the open, XML-based standard for exchanging structured terminological data that allows the transfer of information from one termbase to another.
TMX (TM exchange) is the industry standard format for the exchange of translation memories. SDL TM Server can import a translation memory that is in TMX format and also export translation memories into TMX format.
A translation memory (TM) is a file or database containing source language text segments and the corresponding translated segments. Each pair of source and translated segments is called a translation unit (TU). In a TM, the source language segments are all in one language. A TM may contain translations into several languages but often has just one target language. A TM also contains supplementary data for each TU, such as who created the TU and when. This data is held in fields. A user can also add user-defined data to TUs. TMs allow translators to re-use translations, thus reducing translation time and effort, and increasing consistency.
A file type that was used for TRADOS TagEditor files; it is also the file name extension for this type of file.