Translation Memory

Smartling's SmartMatch

This article will walk you through the following:

What is SmartMatch?

A SmartMatch occurs when a new source string matches perfectly a string in the Translation Memory. However, unlike 100% matches, SmartMatches require additional metadata, such as tags, placeholders, variants, whitespace, and capitalization (case-sensitivity), to be an exact match. Also unlike 100% matches, SmartMatch allows your content to skip the translation step completely, allowing for significant cost and time savings, while ensuring translation consistency.

How SmartMatch Works

When SmartMatch is enabled, once new content is authorized for translation, SmartMatch automatically checks your Translation Memory for an exact match. If an exact match is found, it is automatically applied and the string skips the translation step and moves to the step configured in the SmartMatch Rules - no human effort is required.

Account Owners and Project Managers can customize SmartMatch behavior with SmartMatch Rules, and it can be customized for each Translation Memory source within a leverage configuration. Once a translation memory source is created, you can then enable and configure SmartMatch.

Enable SmartMatch

  1. Do one of the following:
    • In the New Experience, go to Account Settings > Linguistic Assets.
    • In the Classic Experience, go to AssetsLeverage.
  2. From the list of Linguistic Packages, click the name of the package to enter the Linguistic Package
  3. Under Leverage Configuration, click the name of the configuration you want to customize.
  4. In the list of translation memory sources, under SmartMatch, click Disabled/Enabled. This opens the SmartMatch Settings dialog, where you can configure SmartMatch Rules.
  5. Select a result for each SmartMatch rule from the dropdown.
    • If you choose First Revision Step, you have the additional option of selecting or deselecting Enable Pre-Publish.
  6. Click Save Changes to put the customizations into effect or Cancel to exit.

SmartMatch Rules

SmartMatch has different levels of precision. The following rules allow you to consider the context in which the previous translation was used, as well as some formatting elements like spaces or upper and lower case letters. 

  Rule Use Case Example
1.  Restore translation: Exact match for previously removed unpublished translations

When you want to recover and SmartMatch unpublished translations for canceled jobs and deleted files.

Note: it is recommended that this is set to one of the following; First Revision Step: Edit, Review, or Holding.

Content will become available for SmartMatch even if it has not been published. For example, a string can be SmartMatched against a previous translation that has only been saved by a linguist, but has not gone through the entire workflow.

2. Text with variant: Text exact match and variant exact match

When you want strings with the same text, variant, inline tags, and placeholders to SmartMatch.

Note: a string with no variant can match with a string with no variant with this rule.

String will match if the sources are identical sequences of characters, including tags, and the variants for the source strings are also identical.
3. Text without variant: Text exact match regardless of variant When you want strings with the same text, inline tags, and placeholders to SmartMatch, regardless of variant used. Unlike "text exact", character sequence exact does not consider variants, but would respect same text, inline tags, and placeholders. 
4. Text ignoring whitespace: Text exact match and ignore all whitespaces

When the strings have identical sequences of characters, including inline tags and placeholders, and you want them to SmartMatch, regardless of differences in whitespace.

Note: Smartling will apply the SmartMatched translation while maintaining the whitespace from the source.

This rule excludes non-breaking space, as this is considered a character.

For example, this rule will allow the following to SmartMatch:
"Open box"
"Open   box "
5. Text ignore markup: Text exact match and ignore markup When you want strings with the same text and order of inline HTML tags and placeholders to SmartMatch, regardless of differences in HTML tags.

Strings will match if the sources are identical sequences of non-tag characters (i.e. identical source terms), and any one of the following

Identical tags, same position in the string.

For example, this rule will allow the following to SmartMatch:

“Welcome to <b>Smartling</b>”
“Welcome to <b>Smartling</b>”

Identical tags, different position in the string.

For example, this rule will allow the following to SmartMatch:

“Welcome to <b>Smartling</b>”
“<b>Welcome to Smartling</b>”
 

Different tags, same position in the string.

For example, this rule will allow the following to SmartMatch:

“Welcome to <b>Smartling</b>”
“Welcome to <a>Smartling</a>”

The amount of HTML tags used, together with the structure of the string (text-tag-text-tag) is how SmartMatch is evaluated for this rule.

6. Text ignore case: Text exact match and ignore uppercase and lowercase characters

When you want the text to SmartMatch, ignoring case.

Note: Smartling will not maintain the case of the source characters in the translation.

For example, this rule will allow the following to SmartMatch:
"Open box"
"open box"
However, if the source is lower-case, but is matched against a capitalized string, the translated string will also be capitalized. 
7. Match any: Any combination of ignore whitespace, markup, or case

When you want the text to SmartMatch, ignoring both case and whitespace.

Note: only the source whitespace will be maintained in the translation.

For example, this rule will allow the following to SmartMatch:
"Open box"
"open   box"

 

SmartMatch Results

Each SmartMatch rule can be enabled with one of the following results.

  1. Published: Matching strings will bypass all workflow steps and immediately be published.
  2. First Revision Step (Review): Matching strings will jump to the first revision workflow step with primary action "review," bypassing all previous workflow steps. If there is no such workflow step, matching strings will bypass all workflow steps and immediately be published.
  3. First Revision Step (Edit): Matching strings will jump to the first revision workflow step with primary action "edit," bypassing the translation workflow step. If there is no such workflow step, matching strings will bypass all workflow steps and immediately be published.
  4. First Revision Step (Edit, Review, or Holding): Matching strings will bypass the translation workflow step. If there are no other workflow steps, matching strings will immediately be published.

    When choosing to send content to any of the Frist Revision Step results (2-4 above), you can also choose to enable pre-publish. This feature is useful in the event that SmartMatched content remains in a review, edit, or holding step longer than desired. Enabling this setting will allow SmartMatched content to "prepublish" so translations are available to use and are visible in their destination (e.g. on a website via the GDN, or any one of the Connectors) before reaching the Published step on the workflow.

  5. Disabled: If you prefer not to use SmartMatch for a given Translation Memory, ensure that all SmartMatch Rules are set to Disabled and then click “Save Changes”.

    When SmartMatch is Disabled, your translators can still see suggestions from this Translation Memory, but SmartMatch will not automatically move the content to a different step.

Considerations

SmartMatch is a string-level action

In order for SmartMatch to kick in, you need to have a translation available in your memory for the entire string. If there is an existing translation available for just one segment, SmartMatch won’t work. This is to avoid SmartMatching only one sentence within a paragraph, out of context.

Only previously Published translations will SmartMatch

SmartMatch only works if your previous translation has been fully completed and is sitting in the Published step. This ensures that we don’t automatically reuse translations that that have previously gone through the full workflow and reached the Published step.

Translation Memory quality

As SmartMatches bypass your translators completely, they can only ever be as good as the translations stored in your Translation Memory. This means that the quality of your previous translations is a critical factor to consider. 

Think of SmartMatch as a magnifying glass on translation quality. If your Translation Memory contains great quality translations, SmartMatch will help you re-use them at a larger scale and reduce the risk of incorrect re-translations. On the other hand, if your Translation Memory contains poor or even incorrect translations, SmartMatch will keep propagating any mistakes that your translators may have made in the past.

For this reason, SmartMatches should only be sent directly to the Published step if you can fully trust the quality of your Translation Memory. If you are unsure about the quality of the translations stored in your translation memory, it is recommended that SmartMatch Rules are set to an Editing or Review step, so a human can validate that quality.

Workflow setup

When SmartMatch Rules are set to an Editing or Review step, ensure this step type is set up in your workflow. If your workflow does not have this step type configured, SmartMatch will automatically publish any matches.

Is it on or off?

The link text (Enabled or Disabled) indicates whether at least one SmartMatch rule is currently enabled or disabled for the Translation Memory source.

Initiation 

SmartMatch runs continuously, not just the moment strings are authorized, but also after they have been authorized. More precisely, whenever a translation is published or prepublished, it checks to see if anything could SmartMatch from the newly published translation. However, this is not guaranteed to be instantaneous. Therefore, SmartMatched strings may appear in the translation step briefly.

Your Goals

If enabling the Restore translation: Exact match for previously removed unpublished translations rule, consider selecting the First Revision Step (Edit, Review or Holding) result to minimize the probability of an incorrect translation being copied to multiple strings.

Set all SmartMatch rules to Published to maximize cost savings and time-to-market benefit. Selecting First Revision Step and Enable Pre-Publish also maximizes time-to-market benefit.

Recheck for SmartMatches

The SmartMatch feature compares authorized but untranslated strings against existing translations in your leverage configuration to automatically apply translations.

If your project is configured to use SmartMatching, strings are checked for a SmartMatch when they authorized.

However, there are times when you might want to recheck your authorized strings for a SmartMatch.  Examples are:

  • You've imported translations or added a TM after the strings were authorized.
  • You've enabled or updated SmartMatch settings since the strings were authorized.

To recheck strings for SmartMatches:

  1. Go to the Strings View
  2. Select the string(s) you want to recheck for SmartMatches
  3. Click Actions > Recheck for SmartMatches

Strings must first be authorized before they can be SmartMatched.

SmartMatch Reporting

Account Owners and Project Managers can get a data visualization of the number of SmartMatches across the entire account with the SmartMatch Leverage Report.

Was this article helpful?