Translation Memory Management

A translation memory is the database of your translation units. In Smartling the Translation Memory is live in the cloud so it's always up-to-date with the latest translations. Once a translation is saved, it is stored on the translation memory.

Machine Translations are not stored in the translation memory, even if the translation was edited by a translation resource in a post-machine revision workflow step.

Smartling facilitates the creation of new TMs and the management of existing ones. Smartling's Translation Memory Management (TMM) provides powerful search capabilities within a TM, the ability to move content between TMs, delete content, export content, as well as insight into the history of a string within a TM.

Access Translation Memories

Account Owners and Project Managers have access to all Translation Memories for all projects in the Smartling account. To access the translation memory list:

Go to your Account Settings > Linguistic Assets
Click Translation Memories on the left panel

Here, you will find each TM listed, togehter with its source language, and total string count. You can search for a TM, change the view from list to grid, sort the list by name or string count, and create a new TM. Click the ellipses under Actions to find the following options:

Import TMX File to the TM
Export the TM
View more Translation Memory details
Rename the TM
Delete the TM

Create a Translation Memory

Within Smartling, you can create a completely new translation memory or import a TMX file into an existing translation memory. (To apply a TM to a leverage configuration, see Configure Translation Memory Leverage.)

Import a TMX File

A Translation Memory Exchange (TMX) file is a format used for exchanging translation memory data created by a CAT tool. TMX files are useful when you're migrating from another tool or process to Smartling.

To import a TMX into a translation memory, under Actions, click the three dots and select Import TMX File. For more information on TMX files, see Upload a Translation Memory.

For subsequent imports of the same TMX file, with the same naming convention, the previous TMX import will be overwritten.

Export TM

You can export a TMX file of an exisiting TM.

Choose for the TMX to incude the following TM entry metadata:

segment-id
string-variant
tm-uid
project-uid
authorizer (UID)
authorized-date
translator (UID)
translated-date
key
hashcode
file
url

The metadata can be pulled from when the TM entry was first translated or when it was last translated.

First Translated project strings: describes the first time that a translation had been written to this TM from a project. This is useful if you’re looking for older translations that were written to a TM.
Last Translated project strings: describes when the last time a translation had been written to this TM from a project. This is useful if you’re looking for any translations in a TM that had been recently used or updated.

A download link for this export will be sent to your user email address. Larger TM's may take some tome to deliver and download.

View TM Details

To view the details of your translation, click the more icon and select Details. You'll be able to view details about the following:

Created By
Created On
Last Modified By
Last Modified On
Active Package (linguistic package with a direct to it)
Leverage Configuration (with a direct link to it)
Target Language (and the number of strings/words associated with it)
Strings
Words

Rename a TM

To rename a translation memory, click the more icon and select Rename. Enter a new name and click Confirm.

Delete a TM

Deleting an entire TM is permanent and will affect all projects leveraging the TM. (If you think you may want to recover this content in the future, as a workaround, you could create a TM, name it something like "Deleted Content", and then move the unwanted content to this TM.)

Find the TM that you wish to delete. Click the more icon and select Delete TM.

The Delete Translation Memory dialog will appear. In this example, the TM is still being used by a linguistic package.

If the TM is not being used by a linguistic package, you'll be prompted to confirm the deletion.

Enter a Translation Memory

Click the name of any TM to enter, view , and action its content, or translation units.

Translation units are diplayed in a list containing source string with tranlsations, the target language, the last translated timestamp, and a link to view the translation unit's activiy.

Search

Search is based on keyword search, or term-based search and not fuzzy matching, as Smartling uses a different algorithm for that. Search is not case-sensitive.

Term-based search means that if your search includes more than one source keyword, the results returned will include all strings with any of the source keywords and not strings with just the keywords searched for together. For example, when searching for source keyword available topics, the results will return all strings with available and topics as well as available topics.

You can perform a character-based search by simply adding "double quotations" to your source keyword. For example, when searching for the source keyword "available", the results will return all strings with available characters. This will include strings such as unavailable and available topics. To search for strings with a double apostrophe or double quotations, ensure to place double quotations outside the characters, ie """ will return any string with"".

Filters

There are several ways you can search or filter for a string:

Keywords: Source or target keyword
Languages: Target language
Project: Project name
Translation Activity: Authorizer, Date Authorized, Translator, First Translated by, Date Translated
String Metadata: Variant, Key, Hashcode
Content Sources: File, URL, TMX File

Example search: Want to find content translated by a certain user in a specific date-range? Use the Translator and date translated filters. Refine the search further by filtering by target language and project name.

Filters (Classic)

Keywords: Source or target keyword
Languages: Target language
Linguist Action: Name of the user who last saved or authorized the string
Dates: Date last authorized or date that the translation was saved
Project: Project name
String Metadata: Variant, Key
Content Sources: File, URL

Search Multiple TMs At Once

You can search multiple translation memories at once. When you select a TM, you'll see on the left hand side of the page that there's a Translation Memories drop down menu where you can select all TMs or just certain ones from which to search.

If there are TMs containing different source languages that are being searched, the Move and Export actions will not work. For example, if you're attempting to move or export strings from an English (USA) TM to an English (UK) TM. Of course, if all TMs have the same source language, then Move and Export are possible.

Actions

You can move content to another TM, export content from a TM, and delete content within a TM. If the same string is stored in multiple TMs, you will need to move, delete, or edit in multiple TMs.

Move Content to Another TM

Search or filter for strings that you want to move to another TM with the same source language, then select the strings and click Actions > Move. You'll be prompted to select the appropriate translation memory.

Export Content From a TM

Search for strings that you want to export from the TM, then select them and click Actions > Export. You can export an entire translation memory or only export a portion of a TM based on specific search criteria. For example, you might search for only content that was translated in the last six months, and export that as a TMX file.

To export an entire translation memory, without having to click on each individual string, go to your full list of TMs. Click the more icon and select Export TM. All strings within that TM will be exported. An email will be sent to your email address with a link to download the generated TMX file.

Delete Content Within a TM

Occasionally, you may want to pare down your translation memory to ensure that only the most appropriate content is in it. Search or filter for strings that you wish to delete from the TM, and click Actions > Delete. You'll be prompted to confirm the action.

Deleting individual strings is permanent, and will affect all projects leveraging the TM. (If you think you may want to recover this content in the future, as a workaround, you could create a TM, name it something like "Deleted Content", and then move the unwanted content to this TM.) In the future, if the same translation appears again, and is saved, it will be added back to the TM.

Find and Replace

Find and Replace is a powerful feature allowing you to change large numbers of translation memory strings at once. This function applies to actives strings only, inactive strings will not be changed.

To use Find and Replace:

Search for the word you’d like to replace by first searching for a Target Keyword.
Select the strings you’d like to replace.
Click on the Actions button and choose Find and Replace.
In the resulting modal that pops up, fill in the replacement wording in the Replacement Text field.
You may optionally choose to update project strings.
Click Replace.

If multiple strings are selected it may take some time to calculate the number of strings that will be replaced. This is because Find and Replace is more precise in choosing text than the standard Target Keyword search, and does its own search through all selected strings to ensure only the exact characters are replaced.

Bulk Replace

To do a bulk replace, select all strings on the page, then click “Select all strings matching current filter”.

Editing

When hovering over a TM string, you’ll see a link to “Edit Translation”. Clicking this link allows you to edit one string at at time.

This feature allows you to edit one string at a time.

There are no quality checks that are performed here like there are when editing in the CAT tool.

You can:

Save: This updates the translation of the string within the Translation Memory only. Fuzzy matches and SmartMatches in the future will use this new translation.
Save & Update Projects: This updates the translation of your string within the Translation Memory and will propagate to strings within your project that have used the same translation.
Cancel: To cancel any changes that may have been made, and exit editing.

Save & Update Projects

Modifying the full string with ‘save and update projects’ updates the full string and any changed segments in the TM as well as the project.

Modifying a segment with ‘save and update projects’ modifies the segment in TM and project and adds a new full string to the TM reflecting the updated segment. The original full string stays in the TM as well, however it is now unassociated with the project string.

The propagate function can cause updates to your published or pre-published translations. This can trigger downstream behaviors like notifications, Translation Cache refresh, or file download, depending on your integration setup.
This option may not be available. This can be because the translation is not currently active any projects. This can be because it was imported from a TMX; or because a change was already made and saved, but not propagated.

Update Project Strings

Update project strings is an important feature that's available in both single string edit, and Find and Replace. Choosing this option will update the translation of your string within the Translation Memory, and will update strings within projects that have used the same translation. The project strings will be updated in whatever step they're currently in, whether that's a translation step or a published step.

To illustrate how this works, imagine a string in a project called "Business Docs" is translated and saved to the TM. Later, the exact same source string appears in a different project, "Email Marketing". This repetition gets Smartmatched from the translation that was already in the TM. If the TM translation is updated and Update Project Strings is selected, the strings in both "Business Docs" and "Email Marketing" projects will be automatically updated.

View History of a String (Classic)

To view the history of a string (such as the Translator's name, completion date, project name, and the person who authorized the content), click the clock icon within the History column.

For project-specific string history, use the History feature by going to Content > Translations (also referred to as the "List View").

The History of a String in the New UI is found under the Translation Unit Activity

Translation Unit Activity (New UI)

A Translation Unit is the source string and translation entry in the Translation Memory. The Translation Unit is shared across all projects writing to the same Translation Memory. The Translation Unit Actitvy tracks each instance the Translation Unit writes to the Translation Memory. If the Translation Unit is leveraged in a project, including a Smartmatch, this will not display in the activity.

The activity is captured from when the Translation Unit was saved. For TMX entries, the activity is captured when the Translation Unit is uploaded to the platform. For Project entries, the activity is caputed when the Translation Unit is saved in the CAT Tool.

You can view the historic activity of the Translation Unit by clicking the Activity icon in the Translation Memory. The activity captured is;

Type: TMX or Project. This indicated how this Translation Unit entered the TM. TMX upload or saved from a translation made within the Project.

Source: The Project name that is writing to the Translation Memory as the source of the activity entry.

Last Updated: The date and time in which the Translation Unit was last used.

Author: The initial translator (i.e. saved & submitted from a Translation step). The author is N/A for TMX uploads and Smartling API for Smartmatches.

File/URL: the name of the source file/source URL

Key: The key identifier for the translation unit (if any)

Variant: The variant for the translation unit (if any)

Authorizer: The user who authorized the job. It displays jobs-service-jobs-service because of job automation rules. if a user had manually authorized, it would be the user’s name.

Was this article helpful?