Note: This property applies to XLIFF and XLZ formats only. The settings described here also apply to the studioTmSegmentExportLevel property.
WorldServer provides translation memory and terminology database entries for any segment that has fuzzy matches only.
For these segments, WorldServer exports all TD entries, and it exports TM entries in accordance with the user's "minimum score" preference. WorldServer does not export TM or TD entries for any segment that has 100%, multiple 100%, or ICE matches.
This is the default behavior and reflects the way WorldServer currently operates.
WorldServer provides translation memory and terminology database entries for any segment that has fuzzy matches or multiple 100% matches.
For segments with multiple 100% matches, all of the 100% matches and TD entries are exported. Fuzzy matches are exported as well. For segments with no 100% matches, WorldServer exports all TD entries, and it exports TM entries in accordance with the user's "minimum score" preference.
WorldServer does not export TM or TD entries for any segment that has exactly one 100% match or one or more ICE matches.
If the enable_bwb_multiple_exact_matches property in the tm.properties file is not set to true, then multiple 100% matches are not detected and are therefore not exported.
WorldServer provides translation memory and terminology database entries for any segment that has fuzzy matches or that has one or more 100% matches.
For segments with one or more 100% matches, all of the 100% matches and TD entries are exported. Fuzzy matches are exported as well. For segments with no 100% matches, WorldServer exports all TD entries, and it exports TM entries in accordance with the user's "minimum score" preference.
WorldServer does not export TM or TD entries for any segment that has one or more ICE matches.
WorldServer provides translation memory and terminology database entries for any segment that has a match.
For segments with one or more 100% matches or ICE matches, all of the 100% matches and TD entries are exported. Fuzzy matches are exported as well. For segments with no 100% matches, WorldServer exports all TD entries, and it exports TM entries in accordance with the user's "minimum score" preference.
Note: This property applies to WSXZ (Studio) formats only. The settings for this property are the same as for the tmSegmentExportLevel property.
The 4 default setting enables Studio to deliver the same leverage for the package as WorldServer. If you select another value (to reduce the TM/TD content in the package) Studio will have different leverage reports than WorldServer.
When performing segment alignment, use the HTML filter.
Note: We recommend that you use the default value for this property. TMX often does not provide the correct data type. If you set the value of this property to true, the incorrect filter could be used for your content.
WorldServer and Studio 2015 use different locale codes for some locales. If you encounter an error opening a project package you need to create a new mapping. Studio uses the locale codes specified in .NET, which are listed at the following site:
http://msdn.microsoft.com/en-us/library/system.globalization.
cultureinfo%28VS.85%29.aspx
The following mappings are pre-configured by default:
studioLocaleMapping1 = Serbian (Latin), sr-Latn-CS
studioLocaleMapping2 = Serbian (Cyrillic), sr-Cyrl-CS
studioLocaleMapping3 = Azeri (Latin), az-Latn-AZ
studioLocaleMapping4 = Azeri (Cyrillic), az-Cyrl-AZ
studioLocaleMapping5 = Uzbek (Latin), uz-Latn-UZ
studioLocaleMapping6 = Uzbek (Cyrillic), uz-Cyrl-UZ
Errors also appear if the package uses a locale code without a region code, such as en instead of en-US. This mapping fixes that issue:
studioLocaleMapping7 = English, en-US
Remember that studioLocaleMappingN entries must be unique. Add more locales to the list as necessary, as long as you adhere to the given format.
The following colors are configured by default:
bdx.IceMatchColor=LightGray
bdx.ExactMatchColor=PaleGreen
bdx.FuzzyMatchColor=Wheat
bdx.NoMatchColor=White
Controls if the translation kit can be opened in versions of Studio prior to SDL Trados Studio 2015. The backward compatible version will contain the previously available single Project TM (the Idiom.tmx file) in addition to the multiple TMX files respecting the TM Group definition in WorldServer.
Using the backward compatible option can affect the export performance since two TM lookup operations need to be performed. Select this option only if you know that you or your translation team are not using SDL Trados Studio 2014 or later.