Documentation Center

Glossary

100% match

A match that has a score of 100%. A score of 100% is always an exact match. However, an exact match might not be a 100% match (if the translation memory or translation unit is penalized, the score is reduced).

Abbreviation

In translation memories (TMs) for TM Server and Trados Studio, a word that is terminated by a period and is in the TM's list of abbreviations. When a TM is presented with source text, the TM recognizes a period that is part of an abbreviation, and so does not use that period to segment the text. Abbreviations are a language resource.

Activation certificate

A certificate created during offline activation.

Ad hoc entry

A term that is added to MultiTerm from a different application, such as Microsoft Word or Trados Studio.

Alignment

The creation of translation units (TUs) by examining and segmenting the source and corresponding target texts of previously translated content. The alignment process starts with completed translations. It divides the source and target texts into segments, attempting to determine which segments belong together in order to build an aligned translation memory from the content. The resulting translation memory can be used for future translations.

translation alignment

Authorized

If a user has sufficient access rights to perform an action on configuration settings or stored data (for example to update a TM), the user is said to be authorized to perform the action.

Auto-localize

The process of applying automatic localization.

Automated translation

Translation without human interaction. Sometimes called machine translation.
Synonyms
  • machine translation
  • AT
  • MT

Automatic localization

The process by which the software can automatically change the format of numbers, dates and times to suit the target language. For example, when translating English to French, a translation editor can replace the decimal point used in English in 3.141 with a comma as used in French, to produce 3,141. Automatic localization is available if the translation memory (TM) supports it for the TM's placeables. TMS does not apply automatic localization. In Trados Studio and TM Server, automatic localization settings are specified per project for each language pair.

Browser-based editor

An editor that runs within a web browser, and so does not require a lengthy local installation procedure on the local computer. Online Editor is a browser-based translation editor, in contrast to the translation editor in Trados Studio, which is a desktop editor.

online editor

Certificate

A set of letters or numbers generated by the Licenses section of My Account which is used to activate a product offline. You need the activation code and installation ID to generate a certificate. A certificate is either an activation certificate or a deactivation certificate.

Character entity reference

In HTML, XML or SGML a symbolic name for characters. Character entity references start with an ampersand and end with a semi-colon. In between the letters represent the character. For example a non-breaking space is represented by an ampersand followed by the letters nbsp, followed by a semi-colon. See also numeric character reference.

character entity

Compound term

A term consisting of more than one word, for example "local area network".
Synonyms:
  • multi-word units
  • multiple word terms

Concept-oriented

In a concept-oriented termbase, each entry corresponds to a single concept, although an entry may contain multiple synonyms, and homonyms are separated into different entries. MultiTerm is concept-oriented.

Synonym: one concept per entry paradigm

Concordance match

The result of a concordance search that matches all words in the search phrase, but not necessarily in the same order as in the phrase. The translator can pick a match from the list of matches. See also in-order concordance match.

Concordance search

A search through a translation memory (TM) for words or fragments of text within translation units. Contrast with the more common use of a TM, which is to match a whole segment of text at a time. A concordance search is only performed when requested by a user.

Content repository

A folder, file, database or other holder of content.

Context match

A match that takes into account the context within which the match occurs. Usually this means surrounding segments. A context match is even more likely to be correct than a 100% match of a segment. There are different kinds of context match, depending on which aspects of context are taken into account (for example, formatting).

Context view

A near-final form of preview of a translation.

Conversion program

A software program that converts content from its native format to an intermediate format more suitable for translation. Our translation programs like Trados Studio, run a convertor on each translatable item to convert the contents from native format (for example Microsoft Word) to *.sdlxliff format.

Synonyms: convertor

Custom field template

See field template.

Deactivate

The opposite (antonym) of activate, activation.

Synonym: deactivation

Deactivation certificate

A certificate created during offline deactivation. See certificate.

Draft

The translation status appropriate for a translation that a translator has started but has not finished. Typically, if a segment has a fuzzy match in the TM, the translation software inserts the TM translation into the target segment, and marks the segment as draft.

DTD

Document Type Definition. A text file that defines the structure, elements and conventions to which an SGML, XML or HTML document must conform. The DTD file is separate from the document it defines. An example of a widely used DTD is the HTML 4.0 DTD, used to define HTML 4.0 documents.

Document Type Definition

Encoding (character encoding)

A set of rules for representing characters in digital form. One common form of character encoding is Unicode.

Entry class

In MultiTerm, a classification of an entry that MultiTerm uses to define access to the entry. Each entry has one entry class. The entry's current class is held as a field in the entry.

Synonym: MultiTerm entry class

Entry level

In MultiTerm, fields that apply to the whole termbase entry. Entry number, entry class and system fields are always stored at entry level. One of three levels in the entry structure.

Entry number

In MultiTerm, a unique number that MultiTerm assigns to an entry when the entry is created or imported into the termbase. The entry number is stored as an entry level field

Synonyms: concept number, MultiTerm entry number

Entry

An MultiTerm entry consists of a term and its definition. (Deprecated) In relation to a translation memory, a synonym for translation unit.

Exact match

A match in all aspects of text: characters, punctuation and formatting. In an exact match, the text surrounding the source text might be different from the text surrounding the entry in a translation memory (by contrast, a context match requires the same surrounding text.)

Exclusion file

In MultiTerm, a file to which invalid entries are saved during the import process. The exclusion file has an *.xcl extension.

Export definition

A stored specification (termbase object) that defines how data is exported from a termbase to a file.

File

A synonym for a translatable file while it is in a translation editor.

document

File category

See item category.

File path

The name of the file plus the directory path to the file.

File-based TM

A translation memory (TM) that is stored in a file and can be accessed by any user that has access to the file. Contrast to server-based TM.

file-based translation memory

Fragment alignment

This is a fine-grained alignment that takes place at a sub-segment level. Unlike the normal alignment that only takes place at a segment level, with fragment alignment, translated text fragments are matched together with their source counterpart to better leverage the previously translated content.

Fragment match

This is a fine-grained alignment that takes place at a sub-segment level. Unlike the normal alignment that only takes place at a segment level, translated text fragments are matched together with their source counterpart to better leverage the previously translated content.

Fuzzy band

A range for a fuzzy match, for example, 75% to 84%. In TM Server, there is one set of fuzzy bands for all languages in a project.

Fuzzy index

An index that allows you to find misspelled or transposed terms during a fuzzy search or wildcard search.

Fuzzy match

A match that is less than 100%. A fuzzy match has a percentage, for example, it is 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 is more difficult than translating an exact match. A fuzzy match requires more effort and probably needs editing.
Synonyms:
  • fuzzy-match value
  • match value

Fuzzy match threshold

The lowest percentage of a match for the matching text to be used as a fuzzy match. If the match is less than this percentage (which is typically about 75%), then there is no fuzzy match for the text.

Fuzzy match value

See fuzzy match.

Fuzzy search

A type of search by which the application can find terms that are similar or identical to the search text.

Homonym

Words are homonyms of each other if they have the same spelling but different meanings, for example, resign - to sign again, and resign - to leave voluntarily. Normally in MultiTerm, there is a separate termbase entry for each meaning of a homonym.

History fields

MultiTerm uses a set of four system fields that show the edit history for each term: Created on, Created by, Modified on and Modified by. MultiTerm creates and maintains these fields automatically for each entry and term at their respective levels.

History fields are visible in the Full layout and when enabling the Show system fields option in the Default layout.

Import definition

Termbase object that is used to specify import parameters. For example, the import definition specifies how to treat import entries that have entry numbers that already exist in the termbase. The import definition can be saved to the file system as an XDI file.

Inline tag

A markup tag that forms part of a segment. Contrast with structure tag. Common uses of inline tags are to format text, to describe special characters, or to reference an image or other hyperlink. Formatting tags and hyperlinks come in tag pairs. Special character tags and reference tags are usually standalone tags.

Input model

An input model is an MultiTerm feature that defines what fields are displayed to the user. It helps you control the entry of data into termbase entries. Input models are termbase-specific. You can create any number of input models for use with a particular termbase. Different input models can be used by different user groups, ensuring that users only have access to the fields that correspond to their area of expertise.

Installation ID

A unique code which is product and computer specific. This means that a different product on the same computer will produce a different installation code, and vice versa. This code is used when generating activation or deactivation certificates using SafeNet License Manager or within the Licenses section of My Account.

Item

Corresponds to one file, document or other text item that is being translated using desktop translation software, or that accompanies the translatable content. See also, item category. The source of an item is a file, database record, or some other data form. A translatable item needs to be converted into a format such as .sdlxliff before a translator can use a translation editor to translate the content.

Item category

An item is categorized to show how it is used in the translation process. One categorization of items is: Translatable (the item is to be translated), Localizable (to be translated outside the application), Reference (for reference only), Instruction (contains instructions for the translator).

Language pair

A source language and a target language, for example English to French, or English (GB) to French (Swiss). A language pair has direction: English to French is not the same as French to English.

Language resource

Language resources are a set of settings in a translation memory. Each language resource is a list of one of the following: abbreviations, ordinal followers, segmentation rules, variables

Language variant

A specific form of a language used in a culture, for example German is a language (code de), and German as used in Austria is a language variant (code de-AT).

sublanguage

Layout

Termbase object that specifies how you want the entries in your termbase to display in MultiTerm and MultiTerm Online. Use the Layout Wizard to create or modify layouts. You can save the layout to the file system as an XDL file.

Leverage level

The extent to which content can be translated against a TM. The higher the leverage level, the more the TM content is reusable. Leverage levels are generally categorized as High: ICE, SPICE; Medium: exact, 100%; Low: interval fuzzy ranges.

Synonym: leverage

Local translation memory

A translation memory (TM) that is stored on the translator's computer. Usually a local TM can only be used by one user at a time. Compare to server-based translation memory.

Synonym: local TM

Locale

A geopolitical area. In a computer: the settings that define a language, country and other geopolitical variants. Also the two-or four-letter language code used to identify a language or language and language variant. The definition of a culture includes the language variant and the default encoding used to store content in this language (for example, UTF-8).

culture

Main translation memory

A translation memory that is stored on the application database server and is available for all projects. Contrast with project TM.

main TM

Markup

Content in a translatable item that should not be exposed to the translator for translation. This includes layout and formatting information, style definitions, and font information. Markup is almost always coded in the form of markup tags. Embeddable markup is equivalent to an inline tag; non-embeddable markup is equivalent to a structure tag.

Match

An equivalence between two segments of text, usually between a segment of presented text and a source segment in a translation memory. A match has a match score, which is between the fuzzy match threshold and 100%.

Match (filters)

In relation to filters: an equivalence between an entry (for example, a term in a termbase or a translation unit in a translation memory) and a filter rule. Unlike text matches, a filter match does not have a score.

Match band

Segments that are in the same match band have the same unit rates for the purposes of estimating translation time and costs. The match band of a segment depends on the source and target language, and on the quality of match that is found (for example the percentage match in a fuzzy match). Only segments that have a match in a translation memory are classified into match bands.

Match lookup

The process in which presented text is compared with translation units in a TM.

leveraging

Match score

A percentage value that describes the level of equivalence in a match.

Merge

To join two adjacent segments into a single segment.

MTMaster database

MultiTerm master database. In a client/server installation, MTMaster resides on the database server and references all termbases that are stored there. When the MultiTerm client is used as a stand-alone system, MTMaster is stored locally as an MDB file and references all local Jet termbases. See also Database server.

Not translated

A translation status: no translation has been done on the segment. Typically this means that the segment has no translation in the TM, and the translator has not yet produced any translation.

Number

If number recognition is enabled for a TM, the TM recognizes a number in the source text as a placeable. If a segment of presented text matches a translation unit in the TM, except for the value of a number, the TM registers an exact match. For example, if the TM has 'Jane has 5 apples', then it finds an exact match for the presented text 'Jane has 99 apples'. If the TM settings allow it, the translation editor might also auto-localize numbers.

Numeric character reference

In HTML, a numeric representation for characters, given by a number surrounded by an ampersand and a semi-colon. For example an ampersand followed by the characters #160 followed by a semi-colon represents a non-breaking space. See also, character entity reference.

Origin

The origin of a segment's translation.

Origin before adaptation

The origin of a segment's translation before it was changed by the user. For example, when a segment originating from machine translation is then post-edited, the origin before adaptation is machine translation.

Package

A collection of files packaged together and sent to a user or another system. The files in any one package belong to the same project. Examples of packages are project package and return package.

Path name

The full path name is the name of the file plus the directory path to the file.

Penalize

To apply a penalty score. You can penalize translation memories and translation units.

Penalty

A percentage taken away from the score of a match between a translation unit and source text segments. Trados Studio can apply penalties for a variety of conditions: for example a penalty for the translation unit or translation memory used for the match, for formatting differences, and so on. Penalties are specified as project settings.

penalty score

Permission

A right that a user or program has to access an application program, data, files or other resource. Common permissions (access rights) are read, write, delete. Which permissions are required for certain activities on a resource is determined by the software. In TM Server, a user's permissions to a resource are granted by the user's role in a resource library, as specified in an applicable membership list.

access right

Placeholder tag

A markup tag that is inline but, unlike most inline tags, is not a formatting tag. Often a placeholder tag is standalone , for example the img tag.

Plug-in

Software that adds functionality, for example to an application. Users or third parties can create plug-ins for TM Server and for WorldServer by using the SDK.

Preview

A representation of a file in translation that shows how the file will appear after translation. There can be different levels of preview, for example Raw preview (showing the data), Draft preview (showing the result as rendered, but not as published), Standard preview (showing the result as it will be generated).

Project

A project contains a collection of source language files, and associated files (resource files), which TM Server manages as a unit. All files in the same project have the same source language, but can be translated to multiple languages. Unit costs for translation are defined per project, for each target language. Projects have a life-cycle. They go through project stages in a workflow.

Project folder

The Windows folder that holds all the project details, assets and working files.

Project package

A collection of the files needed for a translation, including the translatable items, translation memories, termbases, and instructions, packaged together in a form that can be sent to a user or another system as part of a translation project. (Usually this means they are put in a zip file.) All the files in one project package belong to the same project. All our translation applications allow a project manager to export and import project packages.

Project template

A complete set of project settings, which can be applied as the default settings when creating a project.

Quality model

A set of rules that categorizes translation errors to produce quantifiable measures based on the quality of a translation.

Regular expression

A way of describing a pattern of text, for example: "any five letter word that starts with a capital letter, and ends with a digit". Regular expressions can specify sophisticated text patterns. For this reason they are used to specify segmentation rules. Regular expressions are widely used and are well documented. See, for example, Regular expression.

Reorganize

In a MultiTerm context, reorganizing a termbase updates the fuzzy search index. This speeds up fuzzy searches.

Repeated segment

The first occurrence of a segment that has repetitions.

Repetition

An occurrence of a segment that has been translated previously. Usually the term refers to repetitions within one translatable item, but sometimes it can be used to refer to repetitions across a number of items.

Return package

A package that a member of a project sends to the project manager on completion of translation. See also project package.

Scoping

The process of comparing content to be translated with past translations, to assess the remaining translation cost and effort.

My account

My account is our web portal where you can:
  • purchase and download our software
  • access licenses for certain products
  • purchase and access Support services
  • place and view orders
  • request and view sales quotations
  • purchase and view Certification and Training options

.SDLXLIFF

*.Sdlxliff is an XLIFF format, compliant with XLIFF version 1.2.

RWS has added some standards compliant proprietary extensions.

When you add a translatable item to a project in Trados Studio, Trados Studio converts the item into an *.sdlxliff format file, and preforms all subsequent translation work on the *.sdlxliff file. For example, when you use a Translation Editor, you edit an *.sdlxliff file, and you save the result also as an *.sdlxliff file. The *.sdlxliff file has the same name as the source item but with an added file extension .sdlxliff.

At the end of the project, or when the user generates a final format for review, the translated text is extracted and converted to the destination file format. Usually, the *.sdlxliff working file is kept intact.

Segment

Text that is a single translation unit for the purposes of finding a match in a translation memory. Usually a segment corresponds to a sentence. Translation memories store translations by segment, and segments are also the unit for matching presented text with stored translations. In a translation editor, each segment is displayed on a separate row.

Segmentation

The process of dividing text (usually source text) into segments.

Server-based TM

A translation memory (TM) that is stored on a TM server. A server-based TM can be used concurrently by more than one user. Compare to local TM.

Synonym: server-based translation memory

Source

Descriptive of the original, untranslated item. For example: source content, source language, source segment, source text. Contrast with target. See also, language pair.

Source file

A source file is a program file to be translated in MultiTerm. The file type depends on the parser. For example, the source files for WIN32 are usually .EXE files or .DLL runtime libraries, whereas the source files for the text parser are (structured) text files. The source file may also refer to a database or an SQL query when working with the database parser. The purpose of MultiTerm is to localize these source files. The translated version of the source file is referred to as the target file.

Split

To divide, usually applied to a segment. Some applications allow you to split segments. This can be useful during the translation process to facilitate the translation. WorldServer can also automatically split segments. It does this to look for higher quality matches, and so increase the leverage of the translation memory. Contrast with merge.

Standalone tag

markup tag that can legitimately exist without another closing tag, for example a break tag in HTML. Contrast with tag pair.

Stem

The common root form of a number of words. For example go, going, gone all have the same stem, go. A translation memory can use stems to find matching entries containing word variations. (Verb) To find the stem of a number of words. Stemming can generate a larger number of match hits.

String

The smallest translatable unit of text within a source file is a string. All strings are display and can be edited in the string list window. Each string is assigned to a resource. Strings in a source string list are also called source strings whereas strings in a translation list are referred to as translation string.

Structure tag

A markup tag that exists between segments, and often defines a segment break. Examples are: line break tag, table tag. Contrast with inline tag.

Synonym

Two different terms of the same language referring to the same "thing" (concept). Synonyms should be stored within the same entry as individual terms. Sample: "monitor" and "screen".A word that means the same or nearly the same as another word, such as bucket or pail. Because MultiTerm is a concept-oriented system, synonyms are stored in the same entry.

System objects

These are termbase objects which MultiTerm provides for use with all termbases. For example there are system layouts, system export definitions, system import definitions and a system filter. If you select a termbase object type from the navigation tree in the Catalog view, all available objects of the type are displayed on the right. The word System appears in the Owner column for all system objects.

Tag

A keyword assigned to a portion of text, used to specify text attributes (for example bold format), or text flow attributes (for example a page break). Tags can be categorized into the following, overlapping, categories: Inline or structure; Standalone or one of a tag pair; Translatable or non-translatable.

Synonym: markup tag

Tag pair

A matching pair of markup tags. Most markup tags come as a tag pair: one opening tag and its matching closing tag, for example <b> to represent the start of bold text, and </b> to represent the end of bold text. Contrast with standalone tag.

Target

Descriptive of the translated or destination item, for example: target content, target language, target segment. Contrast with source. See also, language pair.

Target file

A target file is the localized version of a source file. Generally, this is a copy of the source file in which all the resources and strings have been translated to a target language.

Target language

Refers to the language a project is to be translated to. For example, if your project is to translate a manual from English to Spanish, Spanish is the target language.

Target language term

A translation of the search term in the currently selected target language. You can apply special formatting and display properties to target language terms and other target language information.

Target term

First equivalent of the search term in the currently selected target language.

TBX

TermBase eXchange. An XML standard, published as ISO 30042, for the interchange of terminology data, including detailed lexical information.

Termbase Exchange Format

TBX files

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.

Termbase

A database used to store terminology and related information.

terminology database

TD

Termbase object

Any of the following: filter, layout, input model, export definition and import definition. They allow you to work with termbase data. Termbase objects are based on the termbase definition and are termbase-specific.

TMX

TMX (TM exchange) is an industry standard format for the exchange of translation memories. TM Server can import a translation memory that is in TMX format, and can export its translation memories into TMX format files.

Translation Memory Exchange

Token

A token corresponds to a word, or short sequence of words and punctuation marks, in translatable text. When a translation memory (TM) is applied to source text, the TM analyzes the source into tokens. This analysis is independent of the analysis into segments. You can configure a TM to recognize text patterns as single tokens. For example, you can provide an expression that provides a definition of the patterns of text for dates. Such text patterns are called placeables. You can provide rules for translating placeables.

Translation editor

An editor that enables translators to translate bilingual files, such as .sdlxliff files.

Translation memory

A translation memory (TM) is a file or database containing source language text segments and translated versions of the text 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 many languages, but often has just one target language. A TM also maintains 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 reuse translations, thus reducing translation time and effort, and increasing consistency.

TM

Translation status (confirmation level)

The status of review and approval that you can assign to a segment or to a document to indicate the degree of confidence that you have in the translation. The translation statuses of the segments in a document automatically update the translation statuses of the document. Not used in TMS.

TTX

A file type that was used for TRADOS TagEditor files, and also the file name extension for those files. MultiTerm 2021 and later support TTX files and other legacy files via the Trados Compatibility and Migration Power Pack available from the RWS AppStore.

For information on installing apps, see .

TU

An entry in a translation memory (TM), consisting of a segment of source text, its translation text, and supplementary TM data such as translation date. In TMX, translation unit is equivalent to the element TU. (Less common) text which is a single unit for the purposes of matching, equivalent to segment.

translation unit

TM entry

Unicode

A standard for representing characters. It covers most of the world's written languages. A Unicode character is a character that has a Unicode representation.

Unix filter

A matching pair of markup tags. Most markup tags come as a tag pair: one opening tag and its matching closing tag, for example <b> to represent the start of bold text, and </b> to represent the end of bold text. Contrast with standalone tag. A program that processes an input data stream into an output data stream in some well-defined way. Hence, a program that converts a file from one data format to another data format.

UTF-8

An encoding for Unicode characters in one to four bytes. The number of bytes depends on the Unicode character. All the ASCII character codes are single byte UTF-8 codes.

Unicode Transformation Format - 8

Workflow

A model of the stages through which translatable items progress in the translation process.

XCD file

.* xcd files shold the settings used in a MultiTerm conversion session.

XDF file

The file type for a filter definition file saved in XML format.

XDI file

In MultiTerm, the file type for an import definition file saved in XML format.

XDL file

Layout definition file for MultiTerm.

XDM file

Input model file for MultiTerm.

XDT file

Termbase definition file for MultiTerm.

XDX file

Export definition file for MultiTerm.

XLIFF

XLIFF is an XML based file format, designed to be useful for translators.

Some of the features of an *.xliff file are:

  • It is a bilingual file: it holds the source and target language text.
  • It separates translatable and non-translatable content, for example it separates translatable text from formatting information.
  • It structures the translatable content into translatable segments, usually sentences.
  • It holds useful management information, such as the translation status of each segment.

XPath

A syntax for specifying locations in an XML document. It includes path expressions (analogous to file path expressions) and a number of built-in functions. XPath is an important part of XSLT.