Customize SmartMatch Behavior
This article is for Account Owners and Project Managers.
SmartMatch allows you to bypass workflow steps automatically for certain types of matches. SmartMatch behavior can be customized for each translation memory source within a leverage configuration.
SmartMatch has different levels of precision which are evaluated in the below order.
|Use Case||Example||Rule to Use|
|1.||Do you want to recover and SmartMatch unpublished translations for canceled jobs and deleted files?||
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. (For SmartMatching, a date is not a field or parameter that is looked for to SmartMatch against. The date would only be used to indicate the location of the string.)
|Same variant exact including unpublished translations (default)|
|2.||Would you like strings with the same text and order of inline tags and placeholders to SmartMatch?||
Text exact takes into account variant ie. namespace, etc. Strings will match if the sources are identical sequences of non-tag characters, and the number and position of inline tags are identical (the tags themselves can be different).
|3.||Would you like strings with the same text, inline tags, and placeholders to SmartMatch ignoring variant?||Unlike "text exact", character sequence exact does not take into account variants, but would respect same text, inline tags, and placeholders.||Character sequence exact|
|4.||Would you like strings with the same text, variant, inline tags, and placeholders to SmartMatch?||String will match if the sources are identical sequences of characters, including inline tags (same as above). However, the metadata has to match ie. namespace, string hashcode. They also have to be within the same project.||Same variant exact|
|5.||Would you like the text to SmartMatch ignoring both case and whitespace? (Only the source whitespace will be maintained in the translation.)||For example,
|Text ignoring whitespace and case|
|6.||If the strings have identical sequences of characters, including inline tags and placeholders, would you like them to SmartMatch regardless of differences in whitespace? (Smartling will apply the SmartMatched translation while maintaining the whitespace from the source.)||For example,
"Open box "
|Character sequence ignoring whitespace|
|7.||Would you like the text to SmartMatch ignoring case? (Smartling will not maintain the case of the source characters in the translation.)||For example,
"open box"However, if the source is lower-case, but is matched against a capitalized string, the translated string will also be capitalized.
|Text ignoring case|
SmartMatch runs continuously but is not guaranteed to be instantaneous. Therefore, matching strings may appear in the translation step briefly.
If enabling the Same variant exact including 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.
Each SmartMatch rule can be disabled or enabled with one of four results.
- Published: Matching strings will bypass all workflow steps and immediately be published.
- 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.
- 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.
- 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.
Enable or Disable Rules
Account Owners and Project Managers can customize SmartMatch behavior for each translation memory source within a leverage configuration.
- Go to Assets > Leverage.
- Click the name of the leverage configuration you want to customize.
- In the list of translation memory sources, under SmartMatch, click Enabled or Disabled.
- Select a result for each SmartMatch rule. If you choose First Revision Step, you have the additional option of selecting or deselecting Enable Pre-Publish.
- Click Save Changes to put the customizations into effect or Cancel to exit.
The link text (Enabled or Disabled) indicates whether at least one SmartMatch rule is currently enabled for the translation memory source.
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.