The world of translation can be quite simple and straight forward when you have worked with it for a long time. But as tools, services, and service offerings continue to change and grow, it can be quite a daunting task to keep everything straight, especially if you are new to the industry.

We have compiled a few common translation terms from the industry that we hope will clarify the components of your projects, as well as added a few that we use here at Locale to help provide a more cohesive experience.

• Source Language: the source language – sometimes abbreviated SL – is a term that refers to the language of the first document requiring translation. Also known as the language from which the text must be translated.

• Target Language: the target language is a term that refers to the language that must receive the new content from the source document. This is the text which will be created after the translation process has been completed, and results from the use of the source language.

• Language Pair: a language pair – sometimes also written as LP – is the combination of source and target languages. Example: I will need this document translated from English to Spanish" means English and Spanish is the LP required for this project.

• Term Base (TB): a term base – also known as a “translation glossary” – is a list of established terms, usually organized in alphabetical order, that clarifies how terms related to a specific subject area are to be translated from one language into another.

• Translation Memory (TM): a translation memory is a database that stores sentences, paragraphs or segments of text that have been translated before. Each entry, or segment, in the translation memory includes the original language, known as the source, and its translation, known as the target. These TMs are also typically updated after each project and are then used again with future projects to help ensure consistency in all the translations for one client.

• Segment/segmentation: in translation, segmentation is the process of breaking a source text down into smaller units – or segments – for translation. These units are configured by choosing specific segmentation rules – ways in which a source text can be divided into smaller units. Sometimes segmentation is performed by sentence length, paragraph length, line break, etc., which serve as a base for creating and editing translation memories, according to a chosen language pair.

• String/string ID: in the context of a translation platform, a string is a single unit of translation. Translators translate strings one at a time, and each one is saved to the Translation Memory (TM) separately. String IDs are used to define individual strings in a text to provide a more precise way of locating translation text.

• Translation Management System (TMS): a translation management system is a type of software for automating many parts of the human translation process. It can help automate and manage certain actions. Examples of modern TMS systems include XTM Cloud, memoQ, Phrase and Smartling.

• Machine Translation (MT): Machine Translation uses machine-learning approaches to the translation of text from one language to another (source to target), taking into account the contextual, idiomatic and pragmatic nuances of both languages. Examples of MT engines are DeepL, Google Translate, Microsoft Azure and even ChatGPT.

• Localization: Localization refers to the process of translating content to a higher level of specification and cultural accuracy than just a normal word-for-word translation. Localization aims to not just incorporate the words that are translated from one language to another but the changes and adjustments necessary to account for cultural nuances and similar issues, when applicable. Localization is also often written as L10n, as there are 10 letters in between the L and the n.

• Internationalization: Internationalization is the process of preparing a document to be used anywhere in the world, but localized as necessary. This creates a document that is both linguistically deliverable and culturally sensitive for a worldwide audience. Internationalization is also often written as i18n, as there are 18 letters in between the I and the n.

• Locale instance: we often refer to your Locale instance as your main access point for Locale (a trial or paid system). It is the one you log into to create your project workflows.

• Dashboard: when you access your Locale instance, the first thing you see when you log in is your Dashboard. It contains any active projects and activities. You have the option to add more.

• Data source: a data source is the location where your source content resides. For us, this is the first place we look for source content that is to be translated and it is the space we send translations back to when they are completed.

  • Example: in a workflow with AEM and XTM Cloud, AEM would be your data source.

• Processor: a processor is the location where your source content is processed, to create the target content. In this case, it is XTM Cloud.

  • Example: in a workflow with AEM and XTM Cloud, XTM Cloud would be your processor.

• Connector: a connector is the configurable, automated extension that connects your data source to your processor.

  • Example: in a workflow with AEM and XTM Cloud, the AEM connector is used to send content from AEM to XTM Cloud and receive the translated content from XTM Cloud and send it back to AEM.

• Activity: the activity feed lists all projects in your Locale instance. The details displayed for each project include the project name, language pairs, start and finish dates and the project’s current status. There is also a view button which you can select to take a closer look at the project itself. Activities can also be filtered according to date and status.

• Accounts tab screen: the Accounts tab screen contains a list of any/all agency accounts or end client accounts in your Locale instance. The creation and last update dates are also displayed, as well as their status (active, inactive) and a view button which you can select to see more information about an account.

  • Agency accounts: agency accounts are identified by a small “building” icon that is attached to the account logo. Agency accounts can also contain multiple end clients as part of their configuration.

  • End client accounts: end client accounts are identified simply by a logo, which is part of their account.

• Project: a project contains a data source and a processor that, together, create a workflow for translation. The project name is displayed in the Activity view. The default name for a project is “My XXXXX project” but it can be customized easily on the project creation summary page.

  • Projects are also sometimes referred to as a “workflow” when the project and each of its components are under consideration.

• Authentication: authentications are the connections that have been authenticated in a Locale instance. For an end user, this might involve something like authenticated access to a data source such as HubSpot. For an agency, this might refer to something like a TMS authentication to XTM Cloud, in which the agency grants access to the end client, to permit them to send content and project information to the agency’s XTM Cloud instance, or receive it. Authentications have one of 2 statuses:

  • Private: a private authentication is private to the Locale instance and cannot be used outside the owner account.

    • Example: an agency has configured its WPML instance to send content to its own XTM Cloud instance. No one outside the agency organization will have access to either the WPML instance or the XTM Cloud instance.

  • Shared: a shared authentication is an authentication that is used to create delegated connections for end users.

    • Example: an agency creates unique shared connections to its XTM Cloud server. These shared authentications contain server location and API key information for verification.

  • Delegated: Delegated authentications are authentications that have been delegated, or shared, with the end client.

    • Example: an agency makes the “MT onlyˮ workflow authentication available in its Locale instance, where its end client is able to log in and create projects. Consequently, whenever the client needs to send content to the agency for MT-only translation, the client simply selects the delegated authentication option in its Locale instance. This authentication is owned and configured by the agency, to include the specific project template needed for the agency’s workflows, TM settings, etc., which can be configured, owned, and maintained by the agency.