The translation memory repair component

By using repair components, you can define how to correct differences between lookup text and source text, as well as how to correct the target.

To implement repairs:
  1. Identify the difference between the lookup text and the match source text that needs to be repaired. For example, they might differ only by a number.
  2. Identify the match target text that corresponds to the match source text that needs to be repaired. For example, this could be the same number or the number in a different form, such as a localized form.
  3. Repair the match source text. The scoring process is based on the difference between the lookup text and the repaired match source text.
  4. Repair the match target text.
  5. Set the repair penalty. Depending on how effectively or reliably you can repair the target text, you may want to assign a repair penalty to signify the confidence level of the repair.
You can use this repair component for various tasks related to translation repair, such as:
  • Repair differences in words, numbers, or dates.
  • Automate data conversions based on locales, such as converting from the metric system to a different system.
  • Localize numbers, dates, or currencies.
WorldServer supports a repair framework through which you can enable or disable individual repairs for specific locale combinations. This means that you can safely create repairs to address issues in specific language combinations. You can reject the repair for various locale combinations or you can even penalize other combinations where the results may not be as reliable.

Java package: com.idiominc.wssdk.component.tm