Documentation Center

Summary of configurable TM properties

The following tables summarize the TM properties that are supported by WorldServer.

AIS-TM attribute mapping

Property NameDescriptionDefault Value
map_ais_property_to_same_named_tm_attributeDetermines if the value for an AIS property is used to populate the value of a TM attribute with the same name. AIS properties are mapped to TM attributes based on their names.false
rank_based_on_ais_tm_attribute_matchDetermines if AIS-TM mapped attributes are used to rank match candidates and includes both ICE and Exact match candidates. false

Auto-segment locking

Property NameDescriptionDefault Value
enable_auto_segment_lock_on_locked_spice_matchDetermines if asset segments should be locked automatically when the TM entry of the match is locked and results in a SPICE match.false
enable_auto_segment_lock_on_locked_ice_matchDetermines if asset segments should be locked automatically when the TM entry of the match is locked and results in a ICE match.false
enable_auto_segment_lock_on_locked_ice_asset_matchDetermines if asset segments should be locked automatically when the TM entry of the match is locked, the TM entry is from the asset that is being leveraged, and it results in an ICE match.false

Auto-translation

Property NameDescriptionDefault Value
auto_translate_mid_variable_markersSet the characters that can be inside the variable segment.
For example, ":-=" allows the following to be set as variables: SNN:123-35-6565 or ASD=123.
None.
auto_translate_variablesDetermines whether to perform auto translation of number-based labels.
For example, SN:234-35-6456 123ABCD AAA1232324.
true
enable_auto_translateDetermines whether auto translation support is enabled.

WorldServer provides a core implementation for auto-translation. Alternatively, customers can implement their own strategies via the SDK support of TM Services.

true
min_letters_in_wordDefines the minimum number of letters in a word for auto-translation purposes (does not affect scoping).

This requires that the enable_auto_translate property be enabled.

0

Leverage

Property NameDescriptionDefault Value
enable_sid_based_alignmentDetermines whether segment IDs (SIDs) are used during the alignment process if they are available.

If both segments contain SID values, SIDs must match in order for the segments to be aligned.

true
enable_sid_lookupDetermines whether to leverage available SIDs for SPICE matches.true
enable_standard_ice_lookupDetermines whether standard ICE matching will be supported.

If you set this property to false, you disable the standard ICE mechanism and operate only on SPICE matches. For example, you might want to do this when processing Java property files.

The option only affects the leverage process. ICE lookup methods in the SDK will still return standard ICE matches.

true
prefer_previously_matched_assetDetermines whether the matching algorithm should prefer matches from an asset that provided a previous match, on condition that the position of the segment is the same in both assets.

This option prefers obtaining matches from a common source. In most cases, it operates with minimal confusion. However, it can cause strange results when used in sub-optimal TM group configurations.

true
prefer_sid_over_ice_matchesDetermines whether SID matches should have a higher priority than ICE matches.

If you set this property to true, a SID-Preferred ICE (SPICE) match is sought before looking up standard ICE matches. Otherwise, the ICE match is sought before looking for a SPICE match. If all content contains a SID or if no content contains SIDs, the impact of this setting is minimal.

This option has an impact for customer data that is a mix of SID and non-SID based content. Preferring SPICE matches over ICE matches suggests that global (SID) definitions should be preferred over the more localized context as defined for ICE matches. Setting the value to false suggests that SPICE matches should be used in the absence of a more localized context match.

ICE matching derives its context from the asset and surrounding segments, while SPICE matching derives its context solely from the segment identifier.

true
require_asset_match_for_ice Determines whether the ICE condition will require that the TM entry match the TM AIS context of the asset being translated.

If this option is enabled, then no segments for new assets will be ICE matched. Note that path normalization will affect how the TM identifies assets, and therefore can affect ICE results when this option is enabled.

false
require_metadata_match_for_iceDetermines whether the ICE condition will require the TM entry to have the same attribute values as the corresponding mapped AIS properties. If enabled, all mapped attributes much match their AIS property counterparts.
false
require_full_usage_context_for_iceDetermines whether a full usage context is required for all ICE matches. For a full usage context, the TM match must have been translated between segments having the same content as those around the asset segment being translated. This option does not affect SPICE matches.
false
require_non_null_context_for_partial_iceDetermines whether a null context should be enough to register a partial ICE match.

This does not affect full context defined by a previous and next segment being null, as is the case for single segment documents.

true
require_asset_match_for_single_segment_asset_iceDetermines whether the ICE condition will require that the TM entry match the TM AIS context of the asset being translated when the asset only contains a single segment.

If this option is enabled, then a single segment asset can only be ICEd if it has been previously translated. Note that path normalization will impact how the TM identifies assets, and therefore can impact ICE results when this option is enabled.

true
search_all_tms_in_group_for_iceDetermines whether or not all the TMs in the group will be searched unless an ICE match has been found.

As TMs is groups are ordered and prioritized, WorldServer will by default accept 100% matches found in higher priority TMs above ICE matches found in lower priority TMs. Enabling this option will force WorldServer to continue searching lower priority TMs until an ICE match has been found or all TMs have been searched.

Enabling this could impact the performance of the leverage process depending on the TM group and the nature of the data stored within it.

false

Performance

Property NameDescriptionDefault Value
segments_update_batch_sizeThe number of updated segments for which to update the translation memory in batch.

As segments are updated, they are added to a queue. When the queue reaches this size or the transaction is committed, then the translation memory is updated for these segments.

500
lookup_unlocked_ice_matchesDetermine whether unlocked ICE-match segments should be looked up again when a user selects re-apply TM or pre-translate.

Generally, it is not worthwhile to set this option to true. It usually results in extraneous processing by the system only to yield the same results. This might be useful in cases involving an updated TM or changed TM. However, the same can be forced by simply choosing to have the asset re-segmented (though this will take more time).

false
max_bulk_remove_per_queryDefines bulk remove batch size.500
max_fuzzy_results_in_asset_lookupThe maximum number of fuzzy match candidates that are returned from the database.

A SQL query does some coarse filtering to pull a manageable number of entries from the database, and then those candidates are further filtered and scored. This constant controls the size of the candidate list that is returned from the database when doing a full document lookup. Increasing the value increases the likeliness of retrieving or scoring the best fuzzy matches. However, it will also increase the amount of data that needs to be retrieved from the database and processed by WorldServer.

This property is similar to max_bwb_results, but it is applied to the leverage process. This value potentially affects the fuzzy scoping results.

10
max_bwb_resultsThe maximum number of fuzzy results requested by the Browser Workbench and export code.

This number does not guarantee that this number of results will be generated. It controls the number of candidates that are retrieved and processed from the database.

The candidate selection is based solely on the words in the segments. As a result, the fuzzy candidates retrieved may not be the best depending on potential differences associated with punctuation, numbers and placeholders. Increasing this value increases the likeliness of retrieving optimal fuzzy matches. However, increasing this value also affects performance of the associated process.

This value affects fuzzy match lookup, and does not affect ICE or exact match lookup.

10
max_search_resultsDetermines the default value for the TM search results, and for a number of other related processes (including search and replace).

For the TM search, it has been exposed to allow the user to override this value. For the other processes such as search and replace, this value represents the maximum number of search results.

5000
api_tm_max_search_resultsThe maximum number of results returned by a call from SDK or webservices.

This is applied per language pair. For example, if you have three target languages, you will have 3* results.

It applies for concordance search and TM lookup. If no value is specified or if the value is lower than 0, no limit is imposed.

-1
shingle_excluded_charactersDetermines which characters to exclude from shingle tables. Currently excludes excessively common characters such as comma, dot, colon, and latin comma, latin dot, latin colon.

It enables the customer to exclude optimized TM search and shingling support for common non-alpha characters for performance reasons; users can configure which characters fall into this category.

,.:/_-
shingle_index_tablespaceControls index table space for shingle tables.

WorldServer dynamically creates what it refers to as shingle tables for each new TM database configured in WorldServer. These tables are required for the fuzzy matching lookup processes. These tables can grow significantly as the TM grows, and it might be useful to require that they be created in their own database tablespace. The specified tablespace must exist. WorldServer does not create the specified tablespace. Once supplied, WorldServer creates all new shingle tables in this tablespace.

Do not change this option after system setup because it will not be able to find the previously created shingles tables. While this should not create an error condition for WorldServer, it prevents WorldServer from gaining access to and using the old shingle tables, which would result in a loss of all fuzzy matches until the entries are regenerated.

None.
enable_special_shingling_modeShingling mode required for special small segment splits with larger segments.

Using this option may require specifying a larger value for the max_fuzzy_results_in_asset_lookup property to ensure maximum leverage.

false
lookup_count_by_wordsDetermines whether or not to look up the total count of segments when searching by words.false

Scoping properties

Property NameDescriptionDefault Value
min_scoping_scoreDefines the minimal score to be registered for scoping purposes, which happens in conjunction with the segmentation and leverage processes.

If fuzzy matches are sought, the score of the best match is recorded as long as it exceeds this value. Anything less than this value will not be recorded. If no matches exceed this value, than the segment is scoped as a 0% match.

This value also defines the default minimal score for TM matches returned by the SDK TM match lookup process.

0.5

Match scoring

Property NameDescriptionCategoryDefault Value
tm_score_same_stem_penaltyDefines the penalty to be applied when the words being compared are different, but have the same stem.

This property is used only when word stemmers are supported. Words with the same stem are generally related and should be treated as related.

Content level0.05
tm_score_punctuation_penaltyDefines the penalty for punctuation/non-alphanumeric character differences.

This value does not necessarily represent a final score penalty, because it is weighted by the number of occurrences.

Content level0.005
tm_score_capitalization_penaltyDefines the penalty to assess for each capitalization difference.

This value does not necessarily represent a final score penalty, because it is weighted by the number of occurrences.

Content level0.01
tm_score_outer_placeholder_weightDefines the outer placeholder weight (word weight is 1.0). Allows the effective weight of outer placeholders to be set. The effort in correcting placeholder placement may not be the same as correcting a word.

This property allows the weight be to set to establish a relative weight to a word element.

Element weight0.1
tm_score_placeholder_sequence_penaltyDefines the penalty for non-matching sequence numbers.

This value does not necessarily represent a final score penalty, because it is weighted by the number of occurrences.

N/A0.01
sid_mismatch_penaltyDetermines penalty for SID mismatch condition. (0.0 - 1.0).
Rules:
  • If both source and TM match have SID values, if different, apply penalty.
  • If neither have SID values, no penalty.
  • If source has SID, and TM match does not, no penalty.
  • If source has no SID and target does, apply penalty.
Leverage level0.0
maximum_target_length_penaltyDefines the penalty to be applied to a hit with a translation that is too long.Leverage level0.01
tm_score_number_difference_penaltyDefines the number difference penalty.

This value does not necessarily represent a final score penalty, because it is weighted by the number of occurrences.

Content level0.2
tm_score_whitespace_difference_penaltyDefines the penalty to be applied when there are whitespace differences between the source text of the segment and the source text of the TM match.

This is a content based penalty, not a leverage level penalty. Value range should be between 0 and 1.

Content penalty0
tm_score_inner_placeholder_weightDefines the inner placeholder tag weight (word weight is 1.0). Allows the effective weight of embedded placeholders to be set.

The effort in correcting placeholder placement may not be the same as correcting a word. This property allows the weight to be set to establish a relative weight to a word element.

Element weight0.25
tm_score_number_weightDefines the number weight (word weight is 1.0). Allows the effective weight of numbers to be set.

The effort in correcting numbers may not be the same as correcting a word. This property allows the weight be to set to establish a relative weight to a word element.

Element weight0.2
tm_score_extra_placeholder_penaltyThis value determines whether placeholders should be considered in the scoring process. It does not actually represent the applied penalty.

There are two other properties that are reserved for this purpose. If the value is 0, then placeholders are omitted from the scoring process. Setting the value to a number greater than 0 results in the placeholders being used to affect the scoring.

Setting this property to 0 is the same as setting both the tm_score_inner_placeholder_weight and tm_score_outer_placeholder_weight values to 0.

Content level1

Leverage level penalties

Property NameDescriptionAttributesDefault Value
tm_score_asset_mismatch_penalty

This penalty allows you to penalize a TM match if it is not associated with the asset that is being translated.

When assets are translated, matches are created that associated with that asset. As a result, the next time the asset is translated, WorldServer is able to bias the selection of matches based on whether they are associated with the newer version of the asset. If this penalty is set to a value greater than zero, then the leverage process will also penalize matches that are not associated with the asset being translated.

Pay attention when using this penalty, as it affects all matches except SPICE matches. Nonetheless, this option may be useful to you if your quality requirements must take the source asset into consideration when evaluating ICE and exact matches.

If you want to prevent ICE matches against matches from a different asset, you should use the ICE restricting option instead.

Leverage level0
tm_score_metadata_mismatch_penalty

This penalty allows you to penalize matches that do not have a complete set of matching values with the asset for all AIS-TM mapped attributes.

Instead of using physically different TMs to partition translation data, metadata can be used. For instance, you can use a mapped attribute to track the product with which the TM entry is associated.

If the products are significantly different in the terminology used or in the language, you might want to further restrict the extent to which translations are cross leveraged. The use of this penalty allows you to do that.

Leverage level0
tm_score_multiple_exact_match_penalty

This penalty allows you to penalize exact matches that occur when there are other exact matches for the segment with differing translations.

Exact matches are ranked using the same rules for ICE matches, and generally will provide the best available match. Nonetheless, perhaps the existence of multiple translations for a segment implies the introduction of a quality issue. There is already the option to detect multiple exact match segments; however, the target segment will still be populated with the system's best guess for the exact match.

If you are not comfortable with WorldServer choosing the best exact match for you, you could choose to penalize such matches so that they would be available to the translator as high fuzzy matches (or whatever leverage level as dictated by the penalty) instead of them being positioned solely for review as an exact match.

Leverage level0
tm_score_unreviewed_match_penalty

This penalty affects all matches, including SPICE and ICE.

If you want to prevent ICE matches against unreviewed matches, you should use the ICE restricting option instead.

Leverage penalty0
tm_score_reverse_leverage_penalty

This penalty allows you to penalize all reverse leverage matches.

In WorldServer, TM content can be leveraged in both directions: source to target, and target to source. This is referred to as bi-directional leverage support. The maximum leverage level supported for reversed leverage matches is 100%. If a reverse leverage match results in a 100% match, it is treated the same way a normal, forward leveraged match – it will be populated into the target segment.

Depending on your quality metrics, this may or may not be acceptable. You may want them to only be treated as high fuzzy matches. If this is the case, then this penalty can be used to prevent reverse leverage matches from generating 100% matches, and thus, prevent the target segment from being auto-populated with them during the leverage process.

Leverage level0

Split/Merge

Property NameDescriptionDefault Value
do_ice_automatic_splitDetermines whether automatic splitting is attempted during ICE matching processes.

If this is disabled, then all splits are disabled. If the split does not result in an ICE match, then it should be undone unless 100% splits option is enabled.

Note that this option does not require that both parts of the split result in ICE matches. It is geared toward finding an ICE match for the first of the two new segments.
true
do_ice_automatic_mergeDetermines whether automatic merging is attempted for ICE matches.

For the ICE option, merging attempts to restore ICE matches that have resulted from segments that have been manually merged and translated by a translator. Without this capability, WorldServer cannot restore the manually merged segment.

Note that manually merging segments goes against the segmentation rules applied by file types. Merging is only attempted when a suitable match has not been found for the current segment being processed.
true
do_100%_automatic_splitEnable splitting during 100% lookup.

If this is disabled, then fuzzy splits are also disabled. If the split does not result in a 100% match, then it should be undone unless the fuzzy split option is enabled.

Note that this option does not require that both parts of the split result in 100% matches. It is geared toward finding a 100% match for the first of the two new segments.

false
do_100%_automatic_mergeEnable merges to produce 100% matches.

If this is disabled, then all fuzzy merge options are also disabled. If a 100% or better match does not result, then all segments involved in the merge should be restored, unless the fuzzy merge option is enabled.

true
do_fuzzy_automatic_splitDetermines whether automatic splitting is attempted for fuzzy matches.
false
do_fuzzy_automatic_mergeDetermines whether automatic merging is attempted for fuzzy matches.

For fuzzy matches, the objective is to combine asset segments so that they collectively yield a higher scoring match in the TM. Merging is only attempted when a suitable match has not been found for the current segment being processed.

true
do_hyper_mergeDetermines whether hyper (formatting insensitive) merging is attempted.

This is similar to the auto merge options. However, this one can only be used in the fuzzy matching process. The standard merge is sensitive to placeholders (formatting). This merge allows for segments to be merge based on content alone. This merge will most likely not result in 100% matches, but it will result in higher fuzzy leveraging. It is designed to compensate for changes in segmentation rules (whether manual, migrated from other TMs or the result of file type configuration changes.) It also helps increase leverage across different document types where the number or types of formatting encodings may not be consistent.

Merging is only attempted when a suitable match has not been found for the current segment being processed.

true
enable_retro_mergeDetermines whether the retro portion of merging is enabled.

Merging has to be enabled in order for this process to be utilized. Retro merge enables the merge process to capture use matches for a given segment to determine if the segment preceding it could be merged with it to generate a better match.

true

Browser Workbench

Property NameDescriptionDefault Value
bwb_display_updated_to_tm_as_iceDetermines whether segments saved to TM are displayed as ICE. They are displayed as manual by default.false
enable_bwb_multiple_extract_matchesIn Browser Workbench, segments with multiple 100% candidates are now identified by a different border style, featuring double solid blue lines. By default, this feature is disabled, because it affects performance during 100% matches.false

Storage

Property NameDescriptionDefault Value
save_untranslated_segmentsDetermines whether untranslated segments in the Browser Workbench are saved in the TM as translations.

Enable this property when you want WorldServer to save empty targets for segments that are intentionally not translated. Not saving to the TM allows the target to be generated without translating the given segment. However, if the asset is updated later, new TM entries that match the untranslated segment may be used.

This option allows an empty translation to be stored and associated with this asset. Note that if an empty translation is stored, it becomes a possible candidate for future documents as well, which might or might not be desirable.

false
save_empty_translated_segmentsDetermines whether translated segments containing only whitespace or placeholders can be stored in the TM when an asset is saved.

This option applies system-wide to determine whether WorldServer allows TM entries to be stored that do not contain a translation. This option applies to new TM entries, and does not affect entries that have already been saved in the TM.

Note that the save_untranslated_segments property applies only to Browser Workbench behavior. This option supersedes the Browser Workbench-specific option and also applies to custom coded processes.

true
import_empty_translated_segmentsDetermines whether translated segments containing only whitespace or placeholders can be imported into the TM from a TMX file. This system-wide option applies to new TM entries, and does not affect entries that have already been saved in the TM.false
save_ice_match_segmentsDetermines whether ICE matched segments are saved during the update TM process.

If set to false, then ICE matches are not saved. If set to false, even if the ICE matches are associated with the current asset already, they still are not saved since they are already in the TM.

Similarly, if set to true, and the ICE matches are already associated with the current asset, they still are not saved since they are already in the TM. If set to true, and the ICE matches were derived from a different asset, then a copy of the TM entry will be created and saved in association to the current asset segment.

If TM groups are used, you may want to set this value to true to ensure that the entry is saved in the associated write TM. If the write TM already contains that (identical) entry, then it will not re-save the entry. This value is false by default.

false
enable_tm_entry_locking_for_locked_segmentsWhen set to true, the TM entry is locked when you lock a segment.true

Repair

Property NameDescriptionAttributesDefault Value
prevent_all_segment_repairsDetermines whether all repairs are disabled.

Setting this value to true disables all TM repairs regardless of their individual settings. Setting it to false disables the option, thus allowing repairs to be executed based on their default or configured settings.

N/Afalse
min_unrepaired_score_for_upgradeThe minimum unrepaired score for a match that can be upgraded to a 100% score.

The upgrade occurs only when the repaired score is 100%. If the unrepaired score is less than this value, then it will never be upgraded to a 100% match.

N/A0.8
capitalizationThis type of repair attempts to ensure capitalization consistency of replaced text to that of the original text.
This works in conjunction with the word transform repair.
  • target_languages=all
  • enabled=true
all and true
number_deletionThis type of repair attempts to delete extra numbers from the TM match text.
  • target_languages=all
  • enabled=true
all and true
number_transformThis type of repair attempts to handle number differences between the segment text and the TM match text.
  • target_languages=all
  • enabled=true
all and true
placeholderThis type of repair attempts to address formatting differences between the segment text and the corresponding TM match. It allows a penalty to be assessed against placeholder repairs that WorldServer does not consider safe.
  • target_languages=all
  • enabled=true
  • unsafe_repair_penalty=0.0
0.0
punctuationThis type of repair attempts to align the outer punctuation of the TM match to that of the source segment.
  • target_languages=all
  • enabled=true
all and true
word_deletionThis type of repair attempts to delete extra words from the TM match text.
  • target_languages=all
  • enabled=true
all and true
word_transformThe current implementation of this type of repair seeks to transform untranslated text in the source and target text of the match to match that of the source segment.

Do not use this type of repair with languages that share common words.

  • target_languages=all
  • enabled=false
false

Live TM Mode Properties

Property NameDescriptionDefault Value
enable_live_translation_memoryDetermines if WorldServer is using Live Translation Memory.

If you set the value to false, TM update behaves largely the same as in WorldServer 8.0. If you set the value to true, WorldServer TMs are updated whenever the segment cache is updated using translation statuses.

true
set_translation_statusesDetermines if segment translation statuses are set at leverage time based on statuses of TM matches.

In live mode, this is always the behavior and there is no way to turn it off (this property setting is ignored). In non-live mode, if this property is set to "true", then ICE matches lead to a segment status of Reviewed, and 100% matches lead to a segment status of Pending. In non-live mode, the default behavior is that segment translation status are not set based on TM matches, as in WorldServer 8.0.

true
maximum_exact_translation_statusThe maximum segment translation status for 100% matches. By default, 100% matches lead to an asset segment translation status of "Pending Review".Pending
require_reviewed_status_for_iceDetermines if translation entries must have Reviewed translation status as a requirement for ICE matches.

The default behavior is that unreviewed translation memory entries do not satisfy the ICE criteria. In non-live mode, all translation memory entries are reviewed, so ICE matches are unaffected by this configuration. This option should affect both SPICE and ICE matches.

true

Miscellaneous properties

Property NameDescriptionDefault Value
tm_newline_separator_keyword Determines the keyword which is used for marking the new line separator.

By default, the value is [NL]. This is the code used in the Search and Replace tool to represent a new line character.

[NL]
normalize_target_in_compatible_modeDetermines whether the target segment normalization is done in a compatible mode.

The compatible mode is used until WorldServer 9.0, where only letters and digits are preserved in the normalized text. The default behavior since WorldServer 9.0.1 is to take the TM match scoring penalties into account. For example, if tm_score_whitespace_difference_penalty is 0, whitespaces are normalized. This property affects how multiple exact matches are found.

false
enable_preserve_tm_entry_identifiersThis property determines whether TM entry identifiers are unchangeable. By default, TM entry identifiers are changeable; they change whenever the TM entry is updated.true
scoping_modeSpecifies whether legacy WorldServer 9.x or Studio-aligned scoping and leverage implementation is used for translation projects or ad-hoc translation jobs.

This will be used as the default setting in WorldServer. Allowed values are "worldserver9x" and "studio".

worldserver9x

Studio scoping mode settings

Property NameDescriptionDefault Value
studio_missing_formatting_penaltyThe missing formatting penalty is triggered if the source segment does not contain any tags, but the translation unit's source segment does. In this case, all aligned tags are dropped from the translation proposal and the penalty will be set. Unless there are target-only tags in the translation unit which cannot be resolved against the current filter's quick tag list, the different formatting penalty will not be triggered in addition.0.01
studio_different_formatting_penaltyThe different formatting penalty is applied if the translation memory and the source document have different formatting, or if additional formatting in the translation memory target segment cannot be fully resolved by using filter-specific quick tag information.0.01
studio_auto_localization_penaltyThe auto-localization penalty is applied during auto-substitution if auto-localization was applied. It is used to guarantee that exact matches produced by auto-substitution will be reviewed. Note that this penalty is not applied during tag-related auto-substitutions.0.00
studio_enable_recognize_datesEnables or disables recognition for date placeables.true
studio_enable_recognize_timesEnables or disables recognition for time placeables.true
studio_enable_recognize_numbersEnables or disables recognition for number placeables.true
studio_enable_recognize_measurementsEnables or disables recognition for measurement placeables.true
studio_enable_recognize_acronymsEnables or disables recognition for acronym and URL placeables.

Note that neither placeable type is auto-substitutable.

true
studio_enable_auto_substitution_for_datesEnables or disables auto-substitution for date placeables.true
studio_enable_auto_substitution_for_timesEnables or disables auto-substitution for time placeables.true
studio_enable_auto_substitution_for_numbersEnables or disables auto-substitution for number placeables.true
studio_enable_auto_substitution_for_measurementsEnables or disables auto-substitution for measurement placeables.true
studio_auto_substitution_measurements_spacingSpecifies if a space is automatically placed between the number and unit in a measurement when translated. For example, you could choose to auto-localize 4km as 4 km.
Possible values are:
  1. DocumentSource – Use the same spacing between the number and the unit that is used.
  2. TmTarget – Use the same spacing between the number and the unit that is used.
  3. None – Never use a space between the number and the unit.
  4. NormalSpace – Always insert a normal space between the number and the unit.
  5. NonBreakingSpace – Always insert a non-breaking space between the number and the unit.
  6. CustomSpace – Use a custom space between the number and the unit.
DocumentSource
studio_auto_substitution_measurements_custom_spaceSpecifies the Unicode character that you want to be used as a space in the auto-localized measurement. For more information about the different spacing Unicode characters, see http://www.unicode.org.None.

Bilingual file import properties

Property NameDescriptionDefault Value
enable_import_bilingual_filesIf you set this property to true, a button to import bilingual files is displayed in the TM search page.false

Deprecated properties

Property NameDescriptionDefault Value
allow_punctuation_repairsGlobally enables or disables punctuation repair. This property was replaced with the locale-to-locale mapping implementation. (See the punctuation property above.)true
allow_number_repairs(Never actually supported.)N/A
enable_iceplus_lookupNo longer supported.true
treat_whitespace_as_significant

Replaced in WorldServer 9.0

This property is no longer supported. Remove it from your tm.properties file. If it is included, you will be unable to start WorldServer.

The treat_whitespace_as_significant property in tm.properties has been replaced by a new penalty property, called tm_score_whitespace_difference_penalty. If you had set treat_whitespace_as_significant to false, you now have to set tm_score_whitespace_difference_penalty to 0.

If you had set treat_whitespace_as_significant to true, you now have to set tm_score_whitespace_difference_penalty to the value to which you have set tm_score_punctuation_penalty.

N/A