Below is a list of common terms you might encounter when localizing or using Transifex.

The Transifex Client is a git-like command-line tool that lets you easily work with large volumes of translation files. Using the client, you can sync files between your local device and Transifex without a UI.

Context is information that helps translators understand the meaning behind what they’re translating. This includes providing screenshots and developer notes with each string.

Crowdsourcing is the process of translating with volunteers from your user community. It can be an effective way to translate content if you have a group of passionate users who love your product.

File formats are industry-standard ways of storing and exchanging translation content. Each development framework, programming language, and content platform will generally have its own file format.

The Editor is the environment in Transifex where translators do their work. It lets translators see your source content and submit translations directly from their browsers without handling any files directly. The Editor also provides translators with tools such as Translation Memory and Glossary to help them deliver high-quality translations.

A glossary is a set of key terms, their part of speech, definitions, and translation. Glossaries help ensure consistency in translations. And they can be helpful when working with industry or brand-specific terms. Your Language Service Provider can often help you create a glossary before translations begin.

Translating in context is a new approach to translation aiming to give translators a better context around what they’re translating. In-context translations usually work through a WYSIWYG-style editor. It first lets translators see (and often interact with) the live version of whatever they’re translating. Then, as the translator types a translation, it’s overlaid onto the page, giving the translator immediate feedback on how their translation will look.

Internationalization, often abbreviated as “i18n,” is the process of adapting software to be used in different languages. This includes marking strings in code as translatable so they can be extracted into a separate file for translation.

Issues are questions or problems related to a string. Anyone can open an issue for a string. For instance, a translator could open an issue for a typo in a source string.

Machine Translation is the use of software to translate content. If you’ve ever used Google Translate, you’ve used machine translation. While MT is generally not recommended for customer-facing content, it can be used with human review in a process known as “machine translation with post-editing.”

A Language Service Provider (LSP) is a translation agency. While LSPs will vary in their services, they usually provide professional translation and review services. Some LSPs specialize in a single language. These are referred to as Single Language Vendors (SLVs). Others provide services in multiple languages. These are known as Multi-Language Vendors (MLVs).

A locale refers to a language spoken in a specific region. Locales are generally represented with two- or four-letter codes. For example, fr refers to French, and fr_CA refers to Canadian French. Transifex uses the language codes specified by the ISO 639-1 standard.

A project is a container for storing your source content and its translations. Projects in Transifex can be private (visible only to those you invite) or public (visible to anyone).

Resources are the content you’re translating along with their corresponding translations. Let’s say you’re translating the file my_file.po. That file and the translated versions – my_file_fr.po and my_file_es.po would form a single resource.

A source file is the original file containing the text or content that needs to be translated. It serves as the reference for all translations, and it contains the strings written in the project's source language. Common source file formats include .po, .xliff, .json, .yaml, .strings, .resx, and .properties. You can access the full list here.

The source language is the language you are translating from. Put another way: your source language is the language your app or website is originally written in.

A string is a sequence of characters. A string can be a word, phrase, or sentence. It can contain numbers, variables, and even HTML tags. “Save settings” and “Please look at %(url)s for more detail.” are both examples of strings.

A style guide is a set of instructions for translators explaining what kind of capitalization, words, tone, etc., should be used when translating. It’s vital to keeping your brand consistent across languages.

Target languages are the languages you are translating to.

A team in Transifex is a group of people who work together to translate one or more projects. Teams are made of Team Managers, Language Coordinators, Reviewers, and Translators.

Transifex Live is a JavaScript-based technology for translating web content. With it, you can save content directly from your website to Transifex without the need to internationalize or handle files. It also lets you translate in context and publish translations on the fly without needing to wait for engineers to make a deployment.

A translation check is an automated check of a translation against a set of rules. For example, checks can ensure that HTML tags and URLs in the source string are present in the translation. Translation checks ensure translations don’t break your app and the original content is preserved.

A translation file is a file that contains the translated text derived from the source file. Each translation file corresponds to a specific target language and includes translations for all the strings, phrases, or segments present in the source file.

Translation Memory Autofill lets you automatically use 100% TM matches as translations. This saves you time and money as you won’t have to retranslate those strings or manually copy and save translations inside the Editor.

Translation Memory is a database of previously translated strings and their translations. If an untranslated string is similar to a translated string, the translation for the translated string will appear as a suggestion inside the Editor. Each suggestion is marked with a % showing how similar the two source strings are. So, a 100% “match” would mean the two strings are exactly the same. With TM, translators can translate faster while ensuring consistency in their work.

Translation Memory Exchange (TMX) is an industry-standard file format for Translation Memory. It lets you move TM data between systems and tools without losing your translations.

TM leverage is a breakdown of TM matches for a set of strings. It helps you estimate how much new translation work needs to be (or was) done and how much you can rely on the TM. For example, a resource with mostly 95-99% TM matches is likely much more straightforward to translate than one with mostly 60-65% matches.