Documentation Center

exchange.properties file

The exchange.properties file is a Java properties file. It allows you to configure behaviors of the WorldServer Import and Export functions. There are properties in the exchange.properties file that are not documented in the following table. The undocumented properties are for WorldServer internal use only; do not modify them.

The following list of parameters shows you the available configuration options and their descriptions.

catasset.failOnError
true
Rolls back the import of any asset for which a placeholder mismatch error is detected.
false (default)
Imports all valid segments except those for which a placeholder mismatch is detected.
catasset.failOnError.MaxSegmentLength
true
Rolls back the import of any asset that contains a segment that violates the maximum segment constraint.
false (default)
Imports all valid segments except those for which a maximum segment constraint violation is detected.
tmSegmentExportLevel
1 (default)
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.

2
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.

3
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.

4
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.

studioTmSegmentExportLevel
4 (default)

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.

termdb.import.preventDuplicates
true (default)
Enables duplicate detection and prevents duplication of term entries on import.
false
Duplicates are imported as separate term entries.
termdb.import.checkAttributes
true (default)
The values of term and term entry attributes are significant in determining whether two term entries are duplicates.
false
WorldServer compares the terms only, and does not consider the attributes.
termdb.import.overwriteAttributes
true (default)
WorldServer replaces the term and term entry attributes of the term entry in the DB with the attributes of a duplicate import term entry, if any.
false
The existing attributes are unchanged.
enforceXTranslatedUnit
true
Never allows the importation of segments marked as TRADOS XTranslated Units.
false (default)
Allows segments to be imported if they are marked as TRADOS XTranslated Units and they have target changes.
displayXtranslatedWarning
true (default)
Displays a warning message when a segment marked as a TRADOS XTranslated Unit is found and it has been translated.
false
Suppresses this message.
XlzFormat
true (default)
Displays the XLZ format as a choice when exporting translation kits.
false
Hides the XLZ format choice during export.
XliffFormat
true (default)
Displays the XLIFF format as a choice when exporting translation kits.
false
Hides the XLIFF format choice during export.
WsxzFormat
true (default)
Displays the WSXZ format as a choice when exporting translation kits.
false
Hides the WSXZ format choice during export.
TradosTtxFormat
true
Displays the TTX format as a choice when exporting translation kits.
false (default)
Hides the TTX format choice during export.
BilingualDocxFormat
true
Displays the Bilingual DOCX format as a choice when exporting translation kits.
false (default)
Hides the Bilingual DOCX format choice during export.
RegulatorBundle
true
Displays the Regulator Bundle format as a choice if the selected tasks are in review.
false (default)
If set to false, Regulator Bundle will not be displayed.
dropPrivateCharacters
true (default)
Private-use characters are converted to question marks on output and are dropped on input.
false
Private-use characters are preserved as is.
IdiomTmxVersion
1.4 (default)
Write out a TMX header for Version 1.4.
1.2
Write out a TMX header for Version 1.2. Used rarely when a third-party tool does not accept TMX Version 1.4.
determineFilterUsingDatatype
true
When performing segment alignment, use the filter that maps to the datatype of the segment in the TMX file.
false (default)
When performing segment alignment, use the HTML filter.
xliff.markICEMatchesAsTranslated
true
When exporting assets in XLIFF format, mark ICE matches as translate=no in the translation-unit element. This causes smart XLIFF editors to ignore the translation unit altogether, so it is not editable by translators and does not show up in word counts.
false (default)
When exporting assets in XLIFF format, do not mark ICE matches as translate=no in the translation-unit element.
studioLocaleMapping
WorldServer language name, Studio 2015 locale code
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.

bdx.segment.layout
SideBySide (default)
Compare source and target segments vertically in a bilingual DOCX review document.
TopDown
Compare source and target segments horizontally in a bilingual DOCX review document.
Background colors for bilingual DOCX review documents
Determine the background colors of the segments in each TM match status in a Bilingual DOCX file. Any color names that are defined in a .NET System.Drawing.Color class can be used.
The following colors are configured by default:
bdx.IceMatchColor=LightGray
bdx.ExactMatchColor=PaleGreen
bdx.FuzzyMatchColor=Wheat
bdx.NoMatchColor=White
export_backward_compatible_package

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.

true
Exports backward compatible package.
false (default)
Does not enable the export of the backward compatible package.
export.wsxz.tm.type.default
Controls the TM export type selected by default during the WSXZ export. It can have the following values: content, link, content_and_link.
content (default)
Exports the content of the WSXZ package.
link
Exports the link of the WSXZ package.
content_and_link
Exports both the link and the content of the WSXZ package.