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 Pairs: 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 are the LPs required for this project.

• Term Base (TB): A term base – also known as translation glossary – is a list of established terms, usually organized in alphabetical order, that clarifies the use of terms related to a specific subject area 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 with consistency in all the translations for one client.

• Segment / Segmentation: Segmentation in translation 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 by sentence length, paragraph length, line break, etc. – that serve as a base for creating and editing translation memories, according to a chosen language pair.

• Strings / 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 separately to the Translation Memory (TM). String IDs are used to define a specific string within a text, 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, and can help automate and manage certain actions. Examples of modern TMS systems include Phrase, memoQ, Smartling, and XTM.

• Machine Translation (MT): Machine Translation uses machine learning approaches to translation of text from one language to another (source to target) including 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 degree of specification and cultural accuracy than just a normal word-for-word translation. Localization aims to incorporate the necessary changes and adjustments not just for the words from one language to another, but accounts for cultural nuances and things 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 and localized as necessary. The process of creating 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 (trial or paid system) of Locale, the one you log into to create your project workflows.

• Dashboard: When accessing your Locale instance, the first thing you see when you log in is your Dashboard with any active projects, activities, and the option to add more.

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

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

• Processor: We refer to a processor as the location where your source content is processed in order to create the target content. In this case, it is XTM

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

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

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

• Activity: The activity feed shows all projects in your Locale instance. Each project appears with the project name, language pairs, start and finish dates, as well as it’s current status. There is also a view button which can be selected for a closer look at the project itself. Activities can also be filtered according to date and status.

• Accounts: The Accounts tab shows 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 to see more information about an account.

  • Agency Accounts: Agency accounts are indicated with a small building icon that is attached to the logo of the account. Agency accounts can also contain multiple end clients as part of their configuration

  • End client accounts: End client accounts are dhown simply with a logo as part of their account.

• Projects: Projects refer to the combination of a data source and a processor together to create a workflow for translation. This heading can be seen from the activity view where the project name is visible. The default name of a project is “My XXXXX project” bit can easily be customized from the project creation summary page

  • Projects are sometimes referred to as a workflow, when we consider the project and each of it’s components

• Authentications: Authentications refer to the connections that have been authenticated within a Locale instance. In this case, for an end user it may be something like authenticated access to a data source like HubSpot. For an Agency, it may refer to something like a TMS authentication to XTM where the agency grants access to the end client to be able to send / receive content and project information from their XTM instance. Authentications have 2 status:

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

    • Example: An agency has configured their WPML instance to send content to their own XTM instance. No one outside of the agency organization will have access to either the WPML instance, or the XTM instance.

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

    • Example: An agency would create unique shared connections to their XTM server. These shared authentications contain server location and API key information for verification.

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

    • Example: An agency makes the “MT onlyˮ workflow authentication available in their Locale instance where their end-client is able to login and create projects. This way, anytime the client needs to send content to agency for MT only translation, they simply select the delegated authentication option in their Locale instance. This authentication is owned and configured by the Agency to include the specific project template needed for their workflows, TM settings, etc which can be configured, owned, and maintained by the agency.